6686fa6917
The original Remote Controller approach were very messy: a big file, that were part of ir-common kernel module, containing 64 different RC keymap tables, used by the V4L/DVB drivers. Better to break each RC keymap table into a separate module, registering them into rc core on a process similar to the fs/nls tables. As an userspace program is now in charge of loading those tables, adds an option to allow the complete removal of those tables from kernelspace. Yet, on embedded devices like Set Top Boxes and TV sets, maybe the only available input device is the IR. So, we should keep allowing the usage of in-kernel tables, but a latter patch should change the default to 'n', after giving some time for distros to add the v4l-utils with the ir-keytable program, to allow the table load via userspace. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
16 lines
516 B
Plaintext
16 lines
516 B
Plaintext
config RC_MAP
|
|
tristate "Compile Remote Controller keymap modules"
|
|
depends on IR_CORE
|
|
default y
|
|
|
|
---help---
|
|
This option enables the compilation of lots of Remote
|
|
Controller tables. They are short tables, but if you
|
|
don't use a remote controller, or prefer to load the
|
|
tables on userspace, you should disable it.
|
|
|
|
The ir-keytable program, available at v4l-utils package
|
|
provide the tool and the same RC maps for load from
|
|
userspace. Its available at
|
|
http://git.linuxtv.org/v4l-utils
|