From: pbflyingdutchman@googlemail.com
To: linux-media@vger.kernel.org
Subject: Why are there key mapping tables in the kernel for remote controls?
Date: Fri, 29 May 2009 15:25:50 +0100 [thread overview]
Message-ID: <4A1FF06E.8060804@gmail.com> (raw)
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
reply other threads:[~2009-05-29 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A1FF06E.8060804@gmail.com \
--to=pbflyingdutchman@googlemail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox