Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754118AbZLHLXa (ORCPT ); Tue, 8 Dec 2009 06:23:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754056AbZLHLX3 (ORCPT ); Tue, 8 Dec 2009 06:23:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50266 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754034AbZLHLX2 (ORCPT ); Tue, 8 Dec 2009 06:23:28 -0500 Message-ID: <4B1E3727.9090106@redhat.com> Date: Tue, 08 Dec 2009 09:23:19 -0200 From: Mauro Carvalho Chehab User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Jon Smirl CC: Dmitry Torokhov , Krzysztof Halasa , hermann pitton , Christoph Bartelmus , awalls@radix.net, j@jannau.net, jarod@redhat.com, jarod@wilsonet.com, kraxel@redhat.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, superm1@ubuntu.com Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? References: <20091204220708.GD25669@core.coreip.homeip.net> <9e4733910912041628g5bedc9d2jbee3b0861aeb5511@mail.gmail.com> <1260070593.3236.6.camel@pc07.localdom.local> <20091206065512.GA14651@core.coreip.homeip.net> <4B1B99A5.2080903@redhat.com> <9e4733910912060952h4aad49dake8e8486acb6566bc@mail.gmail.com> <20091207184153.GD998@core.coreip.homeip.net> <9e4733910912071644y234beebepd426f9f5760507ce@mail.gmail.com> In-Reply-To: <9e4733910912071644y234beebepd426f9f5760507ce@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1591 Lines: 36 Jon Smirl wrote: > On Mon, Dec 7, 2009 at 1:41 PM, Dmitry Torokhov > wrote: >> That is why I think we should go the other way around - introduce the >> core which receivers could plug into and decoder framework and once it >> is ready register lirc-dev as one of the available decoders. > > The core needs to allow for RF remotes too. > > -Bluetooth remotes are already in kernel somehow, I don't know how they work, > -RF4CE, the 802.15.4 stack has been recently merged, the remotes use a > protocol on top of that. These remotes will hit the consumer market > next year. Sony, Panasonic and other big names are behind this. > -Zwave, the Harmony remotes use Zwave. There is no Zwave support in > the kernel that I am aware of. Zwave is proprietary. > > After these protocols are decoded you end up with scancodes. The > scancodes need to get injected into input somehow and then flow > through the mapping process. Decoding down to the scancodes probably > happens over in the networking code. > > After an in-kernel IR decoder runs it needs to hand off the scancodes > into the input subsystem. This same API can be used by the networking > code to hand off RF scancodes. > Yes, the same core should be able to work with non infra red remotes, but, depending on how the device is implemented. Cheers, Mauro. -- 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/