Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755439AbZLHONp (ORCPT ); Tue, 8 Dec 2009 09:13:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755074AbZLHONo (ORCPT ); Tue, 8 Dec 2009 09:13:44 -0500 Received: from khc.piap.pl ([195.187.100.11]:47685 "EHLO khc.piap.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754966AbZLHONl (ORCPT ); Tue, 8 Dec 2009 09:13:41 -0500 From: Krzysztof Halasa To: Mauro Carvalho Chehab Cc: Dmitry Torokhov , Andy Walls , Jarod Wilson , Christoph Bartelmus , j@jannau.net, jarod@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, superm1@ubuntu.com 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: <1259024037.3871.36.camel@palomino.walls.org> <4B0E8B32.3020509@redhat.com> <1259264614.1781.47.camel@localhost> <6B4C84CD-F146-4B8B-A8BB-9963E0BA4C47@wilsonet.com> <1260240142.3086.14.camel@palomino.walls.org> <20091208042210.GA11147@core.coreip.homeip.net> <4B1E3C1D.7070704@redhat.com> Date: Tue, 08 Dec 2009 15:13:42 +0100 In-Reply-To: <4B1E3C1D.7070704@redhat.com> (Mauro Carvalho Chehab's message of "Tue, 08 Dec 2009 09:44:29 -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: 1230 Lines: 34 Mauro Carvalho Chehab writes: > With RC-5, you have no fields describing the remote. So, all the driver could > do is an educated guess. It can't even do that, e.g. single remotes (even the dumb ones) can send different code groups (addresses) for different keys. > IMO, the better is to have an API to allow creation of multiple interfaces > per IR receiver, based on some scancode matching table and/or on some > matching mask. I think setting the keytables for each logical device would do. I.e. just have a way to create additional logical devices. Each can have its own keytable. The decoders would send their output to all logical remotes, trying to match the tables etc. > It should be possible to use the filter API to match different IR's by > vendor/product on protocols that supports it, That would mean unnecessary limiting. > or to match address/command > tuples on protocols where you just have those fields. Precisely. -- 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/