Messages in this thread | | | Date | Tue, 15 Dec 2009 15:14:02 -0500 | Subject | Re: [RFC] What are the goals for the architecture of an in-kernel IR system? | From | Jon Smirl <> |
| |
On Tue, Dec 15, 2009 at 2:58 PM, Pavel Machek <pavel@ucw.cz> wrote: > Hi! > >> (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 will > 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.
-- Jon Smirl jonsmirl@gmail.com -- 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/
| |