From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? Date: Tue, 15 Dec 2009 15:14:02 -0500 Message-ID: <9e4733910912151214n68161fc7tca0ffbf34c2c4e4@mail.gmail.com> References: <1260070593.3236.6.camel@pc07.localdom.local> <4B1B99A5.2080903@redhat.com> <9e4733910912060952h4aad49dake8e8486acb6566bc@mail.gmail.com> <20091207184153.GD998@core.coreip.homeip.net> <4B24DABA.9040007@redhat.com> <20091215115011.GB1385@ucw.cz> <4B279017.3080303@redhat.com> <20091215195859.GI24406@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20091215195859.GI24406@elf.ucw.cz> Sender: linux-kernel-owner@vger.kernel.org To: Pavel Machek Cc: Mauro Carvalho Chehab , 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 List-Id: linux-input@vger.kernel.org On Tue, Dec 15, 2009 at 2:58 PM, Pavel Machek wrote: > Hi! > >> =A0 =A0 =A0 (11) if none is against renaming IR as RC, I'll do it on= a next patch; > > Call it irc -- infrared remote control. Bluetooth remote controls wil= l > have very different characteristics. How are they different after the scancode is extracted from the network packet? The scancode still needs to be passed to the input system, go through a keymap, and end up on an evdev device. I would expect the code for extracting the scancode to live in the networking stack, but after it is recovered the networking code would use the same API as IR to submit it to input. --=20 Jon Smirl jonsmirl@gmail.com