Hello
Just been trying to get my remote to work for tevii S460 and found it
needed some patchwork in the cx88-input.c file
and adding a key mapping table in one of the files.
Now for vdr I use lircd to get the keys fed into vdr from
/dev/input/event<n>
So this feels like things are done twice, as lircd uses a mapping table
too.
To me it makes sense to keep the mapping tables out of the kernel. You
already see a whole bunch of remotes in the kernel.
You don't really want to make kernel updates for each new type of remote
vendors come out with. Lircd seems to be able to do this too and has a
quick recording tool to setup a new remote.
So what is the history behind having these key mapping tables in the
kernel?
regards
Peter
--
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
