[linux-dvb] WinTV NovaT remote keys - num keys only
linuxtv at nzbaxters.com
Sun May 15 10:20:36 CEST 2005
>> Is there something at the kernel level which defines these
>> 'KEY_RED' etc tags?
> they seem to be found in <kernel-root>/include/linux/input.h
>> it looks like the '0x0b' etc signals are being received,
>> but when they're mapped on to KEY_RED etc they don't work.
>> If I map 0x0b, for the RED key, onto KEY_KP5 the key
>> works. But I only have about 14 "KEY_**" placeholders to
>> play with.
>> Can anyone explain why or what module is understanding
>> KEY_KP5 BUT NOT KEY_RED, KEY_BLUE, KEY_TEXT etc etc etc
> My guess would be that it might be something to do with
> KEY_RED being 0x18e, ie something bigger than 0xff. It
> happens that 0x8e displays as nothing, so if it's getting
> handled mod 256 you'll see nothing unless you go to some
> extra trouble, such as piping the output of tail through
> less. (assuming you have less set up to display control
> characters somehow). ie if "echo -e "0x8e" | less" shows you
> something, it's worth trying piping the tail through less.
Although it doesn't explain why my KEY_LEFT works, which is defined in
<kernel-root>/include/linux/input.h as 105, but my KEY_RIGHT doesn't which
is defined in <kernel-root>/include/linux/input.h as 106.
There is possibly a pattern though. There are no keys that work which are
defined in <kernel-root>/include/linux/input.h as hex numbers : 0xXX
Why are some keys in <kernel-root>/include/linux/input.h defined as hex and
others defined as (what I assume is) decimal?
> What's you're locale?
[root at media vdr]# locale
> (I have one of these remote controls, but haven't even got
> round to putting the batteries in yet)
I think I'd hang on to those batteries for now !! ;)
More information about the linux-dvb