From: David K. <dcg...@dc...> - 2006-09-02 06:40:04
|
I'm pretty sure you will have to add the VID/PID values to the lirc_mceusb2 module. Near the top of lirc_mceusb2.c replace this: -- CODE -- #define VENDOR_PHILIPS 0x0471 #define VENDOR_SMK 0x0609 #define VENDOR_TATUNG 0x1460 static struct usb_device_id usb_remote_table [] = { { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, /* Philips eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_SMK, 0x031d) }, /* SMK/Toshiba G83C0004D410 */ { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, /* Tatung eHome Infrared Transceiver */ { } /* Terminating entry */ }; -- CODE -- With this: -- CODE -- #define VENDOR_PHILIPS 0x0471 #define VENDOR_SMK 0x0609 #define VENDOR_TATUNG 0x1460 #define VENDOR_TOPSEED 0x1784 static struct usb_device_id usb_remote_table [] = { { USB_DEVICE(VENDOR_PHILIPS, 0x0815) }, /* Philips eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_SMK, 0x031d) }, /* SMK/Toshiba G83C0004D410 */ { USB_DEVICE(VENDOR_TATUNG, 0x9150) }, /* Tatung eHome Infrared Transceiver */ { USB_DEVICE(VENDOR_TOPSEED, 0x0001) }, /* Topseed eHome Infrared Transceiver */ { } /* Terminating entry */ }; -- CODE -- Recompile the module, and hope it works :) - David Tomas Dubec wrote: > On Sat, 2 Sep 2006 00:12:24 +0200 > Ian Macdonald <ia...@ca...> wrote: > >> On Fri 01 Sep 2006 at 23:27:14 +0200, you wrote: >> >>> i'm afraid this is not the philips device, as lsusb says "topseed", >>> or is this the same? >> I don't know, but I should have read your lsusb output more closely >> and not just gone on what you were told the device was called at >> purchase time. >> >>> i don't have /etc/lircd.conf because i cant even create one. >> If it's compatible with the Philips device, you won't need to. The >> lirc distribution comes with an lircd.conf.mceusb file. Just rename >> that and try it out. > > hmm, tried it right now, lircd starts, but is not working.. > >>> when inserted, dmesg says (lirc_mceusb2 already modprobed): >>> usb 3-2: new full speed USB device using uhci_hcd and address 3 >>> usb 3-2: configuration #1 chosen from 1 choice >> The fact it's trying to use lirc_mceusb2 sounds hopeful. Have you >> added anything to /etc/modprobe.conf to make it load lirc_mceusb2 or >> is it doing that on its own? > > no, it's not, i modprobed those manualy before connecting. connection > of the device does not load any modules itself. > |