Hi all, I see this is a professional discussion and i am a newbbie, sorry for disturbing you but I think you are making a great job and I wanted to thanks and I hope to contribute with my experience: With Richard's patch https://patchwork.kernel.org/patch/106247/ against kernel 2.6.35 i have my remote (Model no. DSR-0112 you can see in this picture: http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg ) working good with my Hauppauge WinTVMinistick Digital Terrestral TV (in the label i have 120009 LF Rev B!G2 4809 ) as a keyboard. Now my distribution update the kernel to 2.6.36 ( http://www.archlinux.org/packages/core/x86_64/kernel26/ ) and i tried to configure the remote to control my applications (xbmc, xine ...) following this wiki: https://wiki.archlinux.org/index.php/Lirc I have also the lircd.conf from lirc website ( http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112 ) But when I start irw I have no output Contrary to kernel 2.6.35 without patches with the new kernel 2.6.36 I can see the receiver: # cat /proc/bus/input/devices I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="SMS IR (Hauppauge WinTV MiniStick)" P: Phys=usb-0000:00:1d.7-1/ir0 S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb2/2-1/rc/rc0/input9 U: Uniq= H: Handlers=kbd event9 B: EV=100013 B: KEY=100fc312 214a80200000000 0 18000 41a800004801 9e168000000000 10000ffc B: MSC=10 lirc create the device: # ls /dev/lirc* /dev/lirc0 /dev/lircd I does not know if the kernel is loading the correct module... # lsmod | grep lirc ir_lirc_codec 3803 0 lirc_mceusb 14145 0 lirc_dev 11543 2 ir_lirc_codec,lirc_mceusb ir_core 14133 9 ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,rc_rc5_hauppauge_new,ir_rc6_decoder,smsmdtv,ir_rc5_decoder,ir_nec_decoder usbcore 137570 8 usbhid,btusb,uvcvideo,smsusb,lirc_mceusb,uhci_hcd,ehci_hcd ... but even if i do not have output from irw i have an output after this command when i press buttons: # sudo cat /dev/lirc0 PïRïïRïRï:RïRïRïïïRï]ïRïïRïRïRïRïRïïïRï\ïïhïRïRïRïRïR:ï: ïRïRïïïRï]ïRïRïRïRïRïRïRïRïïïRïÒ:ïRïïRïRï:RïRï and finally I have this output with evtest: # sudo evtest /dev/input/event9 Input driver version is 1.0.0 Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0 Input device name: "SMS IR (Hauppauge WinTV MiniStick)" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 2 (1) Event code 3 (2) Event code 4 (3) Event code 5 (4) Event code 6 (5) Event code 7 (6) Event code 8 (7) Event code 9 (8) Event code 10 (9) Event code 11 (0) Event code 28 (Enter) Event code 103 (Up) Event code 105 (Left) Event code 106 (Right) Event code 108 (Down) Event code 113 (Mute) Event code 114 (VolumeDown) Event code 115 (VolumeUp) Event code 116 (Power) Event code 119 (Pause) Event code 128 (Stop) Event code 139 (Menu) Event code 142 (Sleep) Event code 163 (NextSong) Event code 165 (PreviousSong) Event code 167 (Record) Event code 168 (Rewind) Event code 174 (Exit) Event code 207 (Play) Event code 208 (Fast Forward) Event code 353 (Select) Event code 363 (Channel) Event code 365 (EPG) Event code 367 (MHP) Event code 370 (Subtitle) Event code 372 (Zoom) Event code 377 (TV) Event code 385 (Radio) Event code 388 (Text) Event code 392 (Audio) Event code 393 (Video) Event code 398 (Red) Event code 399 (Green) Event code 400 (Yellow) Event code 401 (Blue) Event code 402 (ChannelUp) Event code 403 (ChannelDown) Event code 412 (Previous) Event type 4 (Misc) Event code 4 (ScanCode) Event type 20 (Repeat) Testing ... (interrupt to exit) Event: time 1290812392.908813, type 4 (Misc), code 4 (ScanCode), value 1d1f Event: time 1290812392.908847, type 4 (Misc), code 4 (ScanCode), value 1d1f Event: time 1290812394.148687, type 4 (Misc), code 4 (ScanCode), value 1d14 Event: time 1290812394.148721, type 4 (Misc), code 4 (ScanCode), value 1d14 Event: time 1290812395.041427, type 4 (Misc), code 4 (ScanCode), value 1d1c Event: time 1290812395.041460, type 4 (Misc), code 4 (ScanCode), value 1d1c Event: time 1290812396.132564, type 4 (Misc), code 4 (ScanCode), value 1d3b Event: time 1290812396.132601, type 4 (Misc), code 4 (ScanCode), value 1d3b Event: time 1290812397.075242, type 4 (Misc), code 4 (ScanCode), value 1d3d Event: time 1290812397.075277, type 4 (Misc), code 4 (ScanCode), value 1d3d Event: time 1290812398.215813, type 4 (Misc), code 4 (ScanCode), value 1d16 Event: time 1290812398.215846, type 4 (Misc), code 4 (ScanCode), value 1d16 Event: time 1290812398.910422, type 4 (Misc), code 4 (ScanCode), value 1d25 Event: time 1290812398.910457, type 4 (Misc), code 4 (ScanCode), value 1d25 Event: time 1290812399.605012, type 4 (Misc), code 4 (ScanCode), value 1d17 Event: time 1290812399.605045, type 4 (Misc), code 4 (ScanCode), value 1d17 Event: time 1290812400.249371, type 4 (Misc), code 4 (ScanCode), value 1d24 Event: time 1290812400.249387, type 4 (Misc), code 4 (ScanCode), value 1d24 Event: time 1290812400.944056, type 4 (Misc), code 4 (ScanCode), value 1d1e Event: time 1290812400.944090, type 4 (Misc), code 4 (ScanCode), value 1d1e Event: time 1290812403.126436, type 4 (Misc), code 4 (ScanCode), value 1d37 Event: time 1290812403.126454, type 4 (Misc), code 4 (ScanCode), value 1d37 Event: time 1290812403.672113, type 4 (Misc), code 4 (ScanCode), value 1d15 Event: time 1290812403.672144, type 4 (Misc), code 4 (ScanCode), value 1d15 Event: time 1290812404.316922, type 4 (Misc), code 4 (ScanCode), value 1d36 Event: time 1290812404.316954, type 4 (Misc), code 4 (ScanCode), value 1d36 Event: time 1290812405.011170, type 4 (Misc), code 4 (ScanCode), value 1d30 Event: time 1290812405.011205, type 4 (Misc), code 4 (ScanCode), value 1d30 Event: time 1290812405.755117, type 4 (Misc), code 4 (ScanCode), value 1d35 Event: time 1290812405.755149, type 4 (Misc), code 4 (ScanCode), value 1d35 Event: time 1290812406.648168, type 4 (Misc), code 4 (ScanCode), value 1d01 Event: time 1290812406.648203, type 4 (Misc), code 4 (ScanCode), value 1d01 Event: time 1290812407.094400, type 4 (Misc), code 4 (ScanCode), value 1d02 Event: time 1290812407.640046, type 4 (Misc), code 4 (ScanCode), value 1d03 Event: time 1290812408.235279, type 4 (Misc), code 4 (ScanCode), value 1d32 I have the feeling that you made a good job and I miss just a little step to win! So any futher help would be really appreciated, at least by me but probably I am not the only one: googoling I see others have the same question with his remote that at least in italy is well known as working with linux: http://www.linux-magazine.it/La-TV-a-passeggio-pag_3.htm Thanks again Stefano Pompa 2010/11/26 Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>: > Em 15-11-2010 20:57, Richard Zidlicky escreveu: >> On Mon, Nov 15, 2010 at 04:59:24PM -0500, Andy Walls wrote: >>> On Mon, 2010-11-15 at 16:09 +0100, Richard Zidlicky wrote: >>>> On Mon, Nov 15, 2010 at 07:35:06AM -0500, Andy Walls wrote: >>>>> On Mon, 2010-11-15 at 12:27 +0100, Richard Zidlicky wrote: >>>> >>>>> http://git.linuxtv.org/v4l-utils.git?a=tree;f=utils/keytable;h=e599a8b5288517fc7fe58d96f44f28030b04afbc;hb=HEAD >>>> >>>> thanks, that should do the trick. >>>> >>>> In addition I am wondering if the maps of the two remotes that apparently get >>>> bundled with the MiniStick should not be merged into one map in the kernel sources >>>> so the most common cases are covered? >>> >>> I have a certain case where I would like the maps of two bundled remotes >>> both to be loaded - one an RC-5 and one an RC-6 - for a receiver on the >>> HVR-1850 and friends. >> >> looks a bit more twisted. In the case of the siano reciever it should be >> simpler. Apparently it has been bundled with 2 different rc5 type remotes >> and normal users will have either one of them. So technically it is very >> easy to provide a table that serves both cases. > > What are the keycodes used on your remote? I don't see why not add them to the > Hauppauge keytable. > > Cheers, > Mauro > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
