James Mastros <james@xxxxxxxxxxx> writes: > (This is the > difference with a ps2 keyboard -- a ps2 keyboard gets a map assigned > to it at boottime, so it works out-of-box. This isn't really possible > with an IR remote -- though perhaps rc5 is standarized enough, I don't > think other protocols neccessarly are.) Even with RC5 this isn't really possible. RC5 specifies several classes of remotes, and with a typical HTPC scenario the sensor will pick up more than one remote codeset - e.g. one for the display, one for TV card, and maybe others (all those codes may be coming from a single remote). We have no way to know in advance which one code set is for the PC. The only thing which we can "preconfigure" is the remote bundled with the sensor (card etc). And even this can be incorrect. Several sensors don't came with a remote controller. I think the default sensor->remote assignment may only make sense in userspace, while configuring the mapping. Of course all the above changes when the sensors can't present the "raw" data (IR on/off) but does all the decoding internally (and for example can't decode all RC5 but only keys used on its remote). In such unfortunate cases it has to go to the input layer directly. > Userspace would have to load a keymap; those don't really belong in > kernel code. Of course, userspace could look at the device > identifiers to pick a reasonable default keymap if it's not configured > to load another, solving the out-of-box experince. Precisely. -- Krzysztof Halasa -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
