On Nov 26, 2009, at 12:31 AM, Dmitry Torokhov wrote: > On Mon, Nov 23, 2009 at 11:37:53PM -0500, Jarod Wilson wrote: >> On 11/23/2009 12:37 PM, Dmitry Torokhov wrote: >>> On Mon, Nov 23, 2009 at 03:14:56PM +0100, Krzysztof Halasa wrote: >>>> Mauro Carvalho Chehab<mchehab@xxxxxxxxxx> writes: >>>> >>>>> Event input has the advantage that the keystrokes will provide an unique >>>>> representation that is independent of the device. >>>> >>>> This can hardly work as the only means, the remotes have different keys, >>>> the user almost always has to provide customized key<>function mapping. >>>> >>> >>> Is it true? I would expect the remotes to have most of the keys to have >>> well-defined meanings (unless it is one of the programmable remotes)... >> >> Its the cases like programmable universal remotes that really throw >> things for a loop. That, and people wanting to use random remote X that >> came with the amp or tv or set top box, with IR receiver Y. > > Right, but still the keys usually do have the well-defined meaning, Except when they don't. I have two very similar remotes, one that was bundled with a system from CaptiveWorks, and one that was bundled with an Antec Veris IR/LCD (SoundGraph iMON rebrand). Outside of the Antec remote having a mouse pad instead of up/down/left/right/enter, they have an identical layout, and the keys in the same locations on the remotes send the same IR signal. But the button names vary a LOT between the two. So on the DVD key on the Antec and the MUTE key on the CW send the same signal. Same with Audio vs. Eject, TV vs. History, etc. Moral of the story is that not all IR protocols spell things out particularly well for what a given code should actually mean. > teh > issue is in mapping raw code to the appropriate keycode. This can be > done either by lirc config file (when lirc is used) or by some other > means. The desire to map a button press to multiple keystrokes isn't uncommon either, though I presume that's doable within the input layer context too. >> ... >>>> We need to handle more than one RC at a time, of course. >>>> >>>>> So, the basic question that should be decided is: should we create a new >>>>> userspace API for raw IR pulse/space >>>> >>>> I think so, doing the RCx proto handling in the kernel (but without >>>> RCx raw code<> key mapping in this case due to multiple controllers >>>> etc.). Though it could probably use the input layer as well(?). >>>> >>> >>> I think if the data is used to do the primary protocol decoding then it >>> should be a separate interface that is processed by someone and then fed >>> into input subsystem (either in-kernel or through uinput). >>> >>> Again, I would prefer to keep EV_KEY/KEY_* as the primary event type for >>> keys and buttons on all devices. >> >> Current lircd actually inter-operates with the input subsystem quite >> well for any and all supported remotes if their keys are mapped in their >> respective lircd.conf file using standard input subsystem key names, and >> the lirc daemon started with the --uinput param. lircd decodes the raw >> IR, finds the mapping in its config, and happily passes it along to >> uinput. > > Right. > > I guess the question is what is the interface we want the regular > userspace (i.e. not lircd) to use. Right now programs has to use 2 > intercfaces - one lirc for dealing with remotes that are not using > the standard event interface and evdev for remotes using it as well > as the rest of the input devices. >From the mythtv perspective, using the input layer could yield a better out-of-the-box experience -- users don't have to set up an lircrc mapping that converts key names as specified in lircd.conf into commands (key strokes, actually) that mythtv understands. For example, a button labeled "Play" in lircd.conf has to be mapped to 'p' in ~/.lircrc for mythtv to do the right thing with it. If everything came through the input layer, be that natively or via lircd's uinput reinjection, there would be no need to do that extra mapping step, mythtv would simply handle a KEY_PLAY event. So at worst, one manual mapping to do -- IR signal to standard button name in lircd.conf -- instead of two. But the lircrc approach does also allow more flexibility, in that you can only have a certain app respond to a certain key, if so desired, and remap a key to a different function (KEY_RED, KEY_GREEN, KEY_BLUE, KEY_YELLOW -- what should their default functionality be? I know some users map a pair of those to mythtv's "skip to next commflag point" and "skip to prior commflag point"). Unfortunately, mythtv currently doesn't handle KEY_PLAY, KEY_VOLUMEUP, etc., etc. at all right now, it operates purely on keys commonly found on a standard keyboard. Remedying that is on my TODO list for the next release, if I can carve out the time. -- Jarod Wilson jarod@xxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
