V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
obj-$(CONFIG_RC_MAP) += rc-adstech-dvb-t-pci.o \
|
2010-10-12 05:54:13 +08:00
|
|
|
rc-alink-dtu-m.o \
|
2010-10-18 03:16:13 +08:00
|
|
|
rc-anysee.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-apac-viewcomp.o \
|
|
|
|
|
rc-asus-pc39.o \
|
2012-05-19 17:11:47 +08:00
|
|
|
rc-asus-ps3-100.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-ati-tv-wonder-hd-600.o \
|
2011-08-07 05:18:08 +08:00
|
|
|
rc-ati-x10.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-avermedia-a16d.o \
|
|
|
|
|
rc-avermedia.o \
|
|
|
|
|
rc-avermedia-cardbus.o \
|
|
|
|
|
rc-avermedia-dvbt.o \
|
2010-05-11 02:43:31 +08:00
|
|
|
rc-avermedia-m135a.o \
|
2010-05-08 13:23:37 +08:00
|
|
|
rc-avermedia-m733a-rm-k6.o \
|
2010-10-11 21:59:48 +08:00
|
|
|
rc-avermedia-rm-ks.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-avertv-303.o \
|
2010-10-12 04:31:59 +08:00
|
|
|
rc-azurewave-ad-tu700.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-behold.o \
|
|
|
|
|
rc-behold-columbus.o \
|
|
|
|
|
rc-budget-ci-old.o \
|
|
|
|
|
rc-cinergy-1400.o \
|
|
|
|
|
rc-cinergy.o \
|
2010-08-01 19:02:35 +08:00
|
|
|
rc-dib0700-nec.o \
|
|
|
|
|
rc-dib0700-rc5.o \
|
2010-10-23 07:23:31 +08:00
|
|
|
rc-digitalnow-tinytwin.o \
|
2010-10-11 19:24:00 +08:00
|
|
|
rc-digittrade.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-dm1105-nec.o \
|
|
|
|
|
rc-dntv-live-dvb-t.o \
|
|
|
|
|
rc-dntv-live-dvbt-pro.o \
|
|
|
|
|
rc-em-terratec.o \
|
|
|
|
|
rc-encore-enltv2.o \
|
|
|
|
|
rc-encore-enltv.o \
|
|
|
|
|
rc-encore-enltv-fm53.o \
|
|
|
|
|
rc-evga-indtube.o \
|
|
|
|
|
rc-eztv.o \
|
|
|
|
|
rc-flydvb.o \
|
|
|
|
|
rc-flyvideo.o \
|
|
|
|
|
rc-fusionhdtv-mce.o \
|
|
|
|
|
rc-gadmei-rm008z.o \
|
|
|
|
|
rc-genius-tvgo-a11mce.o \
|
|
|
|
|
rc-gotview7135.o \
|
2010-04-17 05:28:35 +08:00
|
|
|
rc-imon-mce.o \
|
|
|
|
|
rc-imon-pad.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-iodata-bctv7e.o \
|
2012-02-02 05:29:44 +08:00
|
|
|
rc-it913x-v1.o \
|
|
|
|
|
rc-it913x-v2.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-kaiomy.o \
|
|
|
|
|
rc-kworld-315u.o \
|
2012-02-18 13:24:53 +08:00
|
|
|
rc-kworld-pc150u.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-kworld-plus-tv-analog.o \
|
2010-10-12 03:08:13 +08:00
|
|
|
rc-leadtek-y04g0051.o \
|
2010-07-03 12:08:52 +08:00
|
|
|
rc-lirc.o \
|
2010-09-03 04:29:30 +08:00
|
|
|
rc-lme2510.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-manli.o \
|
2011-08-07 05:18:11 +08:00
|
|
|
rc-medion-x10.o \
|
2012-04-02 03:41:46 +08:00
|
|
|
rc-medion-x10-digitainer.o \
|
2012-05-14 20:52:37 +08:00
|
|
|
rc-medion-x10-or2x.o \
|
2010-10-12 06:12:58 +08:00
|
|
|
rc-msi-digivox-ii.o \
|
2010-10-12 07:19:23 +08:00
|
|
|
rc-msi-digivox-iii.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-msi-tvanywhere.o \
|
|
|
|
|
rc-msi-tvanywhere-plus.o \
|
|
|
|
|
rc-nebula.o \
|
|
|
|
|
rc-nec-terratec-cinergy-xs.o \
|
|
|
|
|
rc-norwood.o \
|
|
|
|
|
rc-npgtech.o \
|
|
|
|
|
rc-pctv-sedna.o \
|
|
|
|
|
rc-pinnacle-color.o \
|
|
|
|
|
rc-pinnacle-grey.o \
|
|
|
|
|
rc-pinnacle-pctv-hd.o \
|
|
|
|
|
rc-pixelview.o \
|
2010-04-05 01:06:55 +08:00
|
|
|
rc-pixelview-mk12.o \
|
2010-12-18 01:39:29 +08:00
|
|
|
rc-pixelview-002t.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-pixelview-new.o \
|
|
|
|
|
rc-powercolor-real-angel.o \
|
|
|
|
|
rc-proteus-2309.o \
|
|
|
|
|
rc-purpletv.o \
|
|
|
|
|
rc-pv951.o \
|
2011-01-24 23:18:47 +08:00
|
|
|
rc-hauppauge.o \
|
2010-06-02 04:30:35 +08:00
|
|
|
rc-rc6-mce.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-real-audio-220-32-keys.o \
|
2011-08-07 05:18:12 +08:00
|
|
|
rc-snapstream-firefly.o \
|
V4L/DVB: IR/streamzap: functional in-kernel decoding
This patch makes in-kernel decoding with the stock Streamzap PC Remote
work out of the box. There are quite a few things going on in this
patch, all related to getting this working:
1) I had to enable reporting of a long space at the end of each signal,
or I had weird buffering and keybounce issues.
2) The keymap has been reworked slightly to match actual decoded values,
the first edition was missing the pre-data bits present in the lirc
config file for this remote.
3) There's a whole new decoder included, specifically for the
not-quite-RC5 15-bit protocol variant used by the Streamzap PC
Remote. The decoder, while usable with other recievers (tested with
an mceusb receiver), will only be loaded by the streamzap driver, as
its likely not of use in almost all other situations. This can be
revisited if/when all keytable loading (and disabling of unneeded
protocol decoder engines) is moved to userspace, but for now, I think
this makes the most sense.
Note that I did try to enable handling the streamzap RC5-ish protocol in
the current RC5 decoder, but there's no particularly easy way to tell if
its 14-bit RC5 or 15-bit Streamzap until we see bit 14, and even then,
in testing an attempted decoder merge, only 2/3 of the keys were
properly recognized as being the 15-bit variant and decoded correctly,
the rest were close enough to compliant with 14-bit that they were
decoded as such (but they have overlap with one another, and thus we
can't just shrug and use the 14-bit decoded values).
Also of note in this patch is the removal of the streamzap driver's
internal delay buffer. Per discussion w/Christoph, it shouldn't be
needed by lirc any longer anyway, and it doesn't seem to make any
difference to the in-kernel decoder engine. That being the case, I'm
yanking it all out, as it greatly simplifies the driver code.
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2010-08-08 00:31:40 +08:00
|
|
|
rc-streamzap.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-tbs-nec.o \
|
2010-11-01 03:24:19 +08:00
|
|
|
rc-technisat-usb2.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-terratec-cinergy-xs.o \
|
2010-10-08 08:56:48 +08:00
|
|
|
rc-terratec-slim.o \
|
2011-03-20 01:11:55 +08:00
|
|
|
rc-terratec-slim-2.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-tevii-nec.o \
|
2011-03-24 23:58:48 +08:00
|
|
|
rc-tivo.o \
|
2010-10-12 07:25:44 +08:00
|
|
|
rc-total-media-in-hand.o \
|
2012-11-09 03:14:50 +08:00
|
|
|
rc-total-media-in-hand-02.o \
|
2010-10-11 18:36:54 +08:00
|
|
|
rc-trekstor.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-tt-1500.o \
|
2010-08-09 21:18:32 +08:00
|
|
|
rc-twinhan1027.o \
|
2010-12-27 05:13:30 +08:00
|
|
|
rc-videomate-m1f.o \
|
V4L/DVB: Break Remote Controller keymaps into modules
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>
2010-04-02 14:05:46 +08:00
|
|
|
rc-videomate-s350.o \
|
|
|
|
|
rc-videomate-tv-pvr.o \
|
|
|
|
|
rc-winfast.o \
|
|
|
|
|
rc-winfast-usbii-deluxe.o
|