From: Pedro P. <pa...@gm...> - 2006-01-17 04:45:29
|
Hello Patrick, Please do an "lsusb -v" and send the output regarding the MCE USB receiver to the list. I had a Mitsumi for testing purposes (not anymore) and had to add code to the lirc_mceusb2.c source file because the IDs for the receiver (vendor and product) weren't there. I have yet to submit a patch (I made a backup, got to fetch it..). This is the section for the receivers that are currently supported (from the lirc_mceusb2.c source file http://cvs.sourceforge.net/viewcvs.py/lirc/lirc/drivers/lirc_mceusb2/lirc_m= ceusb2.c?rev=3D1.2&view=3Dauto ): =3D=3D=3D//=3D=3D=3D #define VENDOR_PHILIPS=09=090x0471 #define VENDOR_SMK 0x0609 #define VENDOR_TATUNG=09=090x1460 static struct usb_device_id usb_remote_table [] =3D { =09{ USB_DEVICE(VENDOR_PHILIPS, 0x0815) },=09/* Philips eHome Infrared Transciever */ =09{ USB_DEVICE(VENDOR_SMK, 0x031d) },=09/* SMK/Toshiba G83C0004D410 */ =09{ USB_DEVICE(VENDOR_TATUNG, 0x9150) }, /* Tatung eHome Infrared Transce= iver */ =09{ }=09=09=09=09=09/* Terminating entry */ }; =3D=3D=3D//=3D=3D=3D Your receiver could be a Mitsumi, or something else entirely. If the IDs (vendor and product) are in this list, the problem is something else. Best regards, -- Pedro Palhoto > Date: Mon, 16 Jan 2006 16:00:09 +0100 > From: Patrick Fischer <pat...@gm...> > To: lir...@li... > Subject: MCE USB Receiver > > Hello > After I have detected that I can't use the internal Com2, i want to use > the MCE USB Receiver. > I have seen that there are two driver in the cvs Version. > -Windows Media Center Remotes (old Version , Microsoft USB ID) > -Windows Media Center Remotes (new Version , Philips et al.) > > I have tried this install howto > http://blatter.com/mceusb/INSTALL > > It works fine except I have chosen the lirc own modules for "lirc_mceusb"= . > My problem is that I can't Plugin the Controller because it is included > in my SettopBox. > So I have tried to load the modules by > modprobe lirc_mceusb debug=3D1 > alternative I have reboot the whole system. > > My dmesg don't show me the expected output, it shows me: (for lirc_mceusb= 2) > > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_mceusb2: USB remote driver for LIRC v0.22 > lirc_mceusb2: Martin Blatter <mar...@ya...> > lirc_mceusb2: debug mode enabled > usbcore: registered new driver lirc_mceusb2 > > > and for lirc_mceusb: > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_mceusb: USB remote driver for LIRC v0.3 > lirc_mceusb: Martin Blatter <mar...@ya...> > usbcore: registered new driver lirc_mceusb > > /usr/local/src/lirc# ls -l /dev/lirc* > crw-r--r-- 1 root root 61, 0 2006-01-16 15:13 /dev/lirc > prw-rw-rw- 1 root root 0 2006-01-16 15:13 /dev/lircd > prw-r--r-- 1 root root 0 2006-01-16 15:13 /dev/lircm > > cat /dev/lirc > cat: /dev/lirc: No such device > > mode2 > mode2: error opening /dev/lirc > mode2: No such device > > Maybe somebody know the reason why I can't open the dev/lirc? > > Greetings > Patrick > |