summaryrefslogtreecommitdiff
path: root/linux/drivers/media/dvb/frontends/ves1820.h
diff options
context:
space:
mode:
authorSteven Toth <stoth@linuxtv.org>2008-09-21 23:54:59 -0400
committerSteven Toth <stoth@linuxtv.org>2008-09-21 23:54:59 -0400
commitb1122ac876ec86fd21396d56d215e63543398c2d (patch)
treefa8afdfd3629a5d4b0c51e7eaa1e174772ebe71c /linux/drivers/media/dvb/frontends/ves1820.h
parentdc5d724b55e94616801ab8f3c004cd16ed14bc20 (diff)
downloadmediapointer-dvb-s2-b1122ac876ec86fd21396d56d215e63543398c2d.tar.gz
mediapointer-dvb-s2-b1122ac876ec86fd21396d56d215e63543398c2d.tar.bz2
HVR3000/4000 Hauppauge related IR cleanups
From: Darron Broad <darron@kewl.org> 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. Priority: normal Signed-off-by: Steven Toth <stoth@linuxtv.org> Signed-off-by: Darron Broad <darron@kewl.org>
Diffstat (limited to 'linux/drivers/media/dvb/frontends/ves1820.h')
0 files changed, 0 insertions, 0 deletions