diff options
| author | Darron Broad <darron@kewl.org> | 2008-09-22 00:54:59 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2008-10-12 09:37:06 -0200 |
| commit | 34c080295af9b3ed9f704a881e07eb5ac128e1ed (patch) | |
| tree | af525a9735fbc138e2466f840e0d10f369600429 /drivers/media/dvb/dm1105 | |
| parent | 681faa0b7a1d67576df07e0ad55ca42b2eab174a (diff) | |
| download | op-kernel-dev-34c080295af9b3ed9f704a881e07eb5ac128e1ed.zip op-kernel-dev-34c080295af9b3ed9f704a881e07eb5ac128e1ed.tar.gz | |
V4L/DVB (9016): HVR3000/4000 Hauppauge related IR cleanups
From the author:
This patch-set fixes remote control issues I have experienced
with hauppauge drivers in Linux since the PVR-350 and now
with both a NOVA-S+ and HVR-4000. It has also been confirmed
to work with an HVR-1300 user who had exactly the same issue.
Hauppage remote controls use RC5. RC5 has a bit-field which
represents the target device. The hauppauge windows drivers
have a registry key which can enable filtering, but the linux
drivers will accept any target device in this bit field for
internal processing.
This causes problems with setups such as mythtv where remote
control key presses destined for the TV (target = 0) are
interpreted by the kernel and subsequenctly LIRC then mythtv.
Of the remote controls I have to hand (wintv black, pvr/hvr
silver) the hauppauge remotes send one of two device targets
ids, these are interpreted by the patch which then filters
out any non hauppauge addresses.
Signed-off-by: Steven Toth <stoth@linuxtv.org>
Signed-off-by: Darron Broad <darron@kewl.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/dvb/dm1105')
0 files changed, 0 insertions, 0 deletions
