> >
> >>
> >> You need to search the lirc mceusb2 driver source for the vendor and
> >> product on your ir driver. Some where added in the last months for
> >> Shuttle.
> >
> > I`m using lirc 0.83pre1 as the stable one doesnt compile against
> > kernel 2.6.23. I tried to play with the lirc_mceusb2 source to add my
> > device, but I get a strange error... look:
> >
> > freevo:~# lsusb -v (full output attached)
> > ..
> > idVendor 0x051c Shuttle, Inc.
> > idProduct 0x0005
> > bcdDevice 5.12
> > iManufacturer 4 Shuttle Inc
> > iProduct 28 VFD Module
>
> Are you sure that this is the ir usb device, this is the LCD display.
> What about "Bus 006 Device 002: ID 04cf:0022 Myson Century, Inc."
>
The Myson device is my usb keyboard. as I understand the Shuttle is a
kind of 2-in-1 device, it has the dislplay and the ir receiver. dmesg
shows this:
input: Shuttle Inc VFD Module as /class/input/input5
input: USB HID v1.11 Keyboard [Shuttle Inc VFD Module] on usb-0000:00:1d.2-2
drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt endpoint
input: Shuttle Inc VFD Module as /class/input/input6
input: USB HID v1.11 Device [Shuttle Inc VFD Module] on usb-0000:00:1d.2-2
see? it grabs two two inputs.
yesterday I tried the lirc+devinput but without success.
> You can try adding these and removing the shuttle2. IIRC someone, on the
> lirc list, had a similar problem with their shuttle remote and resolved it
> this way.
>
> >
> > so I changed lirc_mceusb2 and added:
> >
> > #define VENDOR_SHUTTLE2 0x051c
> >
> >
> > /* Shuttle eHome Infrared Transceiver */
> > { USB_DEVICE(VENDOR_SHUTTLE2, 0x0005) },
> >
> >
> > freevo:~# modprobe lirc_mceusb2 debug=1
> > lirc_dev: IR Remote Control driver registered, major 61
> > lirc_mceusb2: Philips eHome USB IR Transciever and Microsoft MCE 2005
> > Remote Control driver for LIRC $Revision: 1.36 $
> > lirc_mceusb2: Daniel Melander <[EMAIL PROTECTED]>, Martin Blatter
> > <[EMAIL PROTECTED]>
> > lirc_mceusb2: debug mode enabled
> > lirc_mceusb2: usb probe called
> > usb 6-2: reset low speed USB device using uhci_hcd and address 3
> > lirc_mceusb2: inbound and/or endpoint not found
> > usbcore: registered new interface driver lirc_mceusb2
> >
> > Since I had a guess about usbhid, I tried to unload usbhid, and load
> > lircmceusb2, and the result is something like a " lirc_mceusb2: found
> > inbound .." followed by a nice oops.
> >
> >>
> >> > mode2 cant find the /dev/lirc device. I tried to mknod the device and
> >> > mode2 still dont find it.
> >> >
> >> > while booting I'm seeing this on dmesg:
> >> >
> >> > input: Shuttle Inc VFD Module as /class/input/input6
> >> > input: USB HID v1.11 Keyboard [Shuttle Inc VFD Module] on
> >> usb-0000:00:1d.2-2
> >> > drivers/hid/usbhid/hid-core.c: couldn't find an input interrupt
> >> endpoint
> >> > input: Shuttle Inc VFD Module as /class/input/input7
> >> > input: USB HID v1.11 Device [Shuttle Inc VFD Module] on
> >> usb-0000:00:1d.2-2
> >>
> >> You can also use the dev/input driver for lirc, there is a page on the
> >> wiki about this.
> >
> > I used dev/input before for a bttv card. I did a minimal test here
> > trying to cat /dev/input/evenX > file, and pressing keys on remote,
> > but only got a empty file. I will try the proper lirc dev/input thing.
> > But since the hid-core is complaining about the endpoint i dont have
> > much hope.
>
--
Christian Lyra
PoP-PR/RNP
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users
