Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752772AbZKZUc7 (ORCPT ); Thu, 26 Nov 2009 15:32:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752720AbZKZUc6 (ORCPT ); Thu, 26 Nov 2009 15:32:58 -0500 Received: from khc.piap.pl ([195.187.100.11]:37319 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751742AbZKZUc5 (ORCPT ); Thu, 26 Nov 2009 15:32:57 -0500 From: Krzysztof Halasa To: Mauro Carvalho Chehab Cc: Jarod Wilson , Dmitry Torokhov , linux-kernel@vger.kernel.org, Mario Limonciello , linux-input@vger.kernel.org, linux-media@vger.kernel.org, Janne Grunau , Christoph Bartelmus Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure References: <200910200956.33391.jarod@redhat.com> <200910200958.50574.jarod@redhat.com> <4B0A765F.7010204@redhat.com> <4B0A81BF.4090203@redhat.com> <4B0AC65C.806@redhat.com> <4B0E765C.2080806@redhat.com> <4B0ED238.6060306@redhat.com> Date: Thu, 26 Nov 2009 21:33:01 +0100 In-Reply-To: <4B0ED238.6060306@redhat.com> (Mauro Carvalho Chehab's message of "Thu, 26 Nov 2009 17:08:40 -0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1206 Lines: 36 Mauro Carvalho Chehab writes: > see include/linux/input.h: > > struct input_event { > struct timeval time; > __u16 type; > __u16 code; > __s32 value; > }; > > extending the value to more than 32 bits require some changes at the > input layer, probably breaking kernel API. Yeah, but that's a "key" space, not "raw code" space. Keys via input and raw codes via lirc and there is no problem. The mapping tables for input layer need to have variable code widths, depending on the protocol, sure. >> I don't think so. We can pass the space/mark data to all (configured, >> i.e. with active mapping) protocol handlers at once. Should a check >> fail, we ignore the data. Perhaps another protocol will make some sense >> out of it. > > What happens if it succeeds on two protocol handlers? We signal both and hope it isn't self-destruct button. We can't fix it no matter how hard we try. -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/