HI all. I artificially binded some drivers (several tries) to the vendor:device in udev/rules.d/ and achieved to add "something" in /proc/bus/usb/devices. I don't know if it's relevant though, or even if it's related... With usbmon, the only activity shown was traffic on bus when device is plugged/unplugged on USB, nothing else, only "Ci" or "Co" frames. Is there a kind of "catch all" dumb driver to bind to this device so that I could see what is the protocol ? Writing an input driver should begin by knowing what's going on, only bulk data dumping, maybe I shoud modify a simple driver like "evdev" or "usbkbd" ? Regards, Chris. Le Tuesday 24 February 2009 00:30:15 Greg KH, vous avez écrit : > On Mon, Feb 23, 2009 at 01:04:40PM +0100, sani.broyeur@xxxxxxx wrote: > > Hi. > > > > I'm a newcommer on this list. I was developper a lonnnnnng time ago, so > > programming should not be a problem for me as far as I can find relevant > > docs and some advices :-) > > > > There seems to be a lack of USB remote control usable with Linux, and I > > don't want to use home made LIRC adapters. > > > > That is why I bought either a iMON Mini and an Pinnacle PCTV remote > > control for experiment, two IR remote control widely available for > > micro$oft OS. > > > > First one (iMON Mini) is recognized as HID by regular driver when hotplug > > but makes it crash when all keys except 3 are depressed on the remote > > control. > > What crashes? The remote, or Linux? > > > After several dozen of tries, usbmon showed that weird usb packets > > where send for keys that crashed the USB stack. I gave up, beeing > > unable to know why with so little evidences of this phenomenon. > > That doesn't sound good, care to send us those oopses and usbmon traces? > > > Second one, the Pinnacle PCTV is sold "for Vista only" and, as expected, > > is not at all recognized. It appears in lsusb as device with type given > > by driver, showing an INPUT and an OUTPUT sub-device, because it can also > > emit IR to remote control regular consummer devices (VCR, DVD, TV, > > toaster, etc, etc). > > > > Not beeing recognized by any driver, it does not appears in > > /proc/bus/usb/devices, beeing impossible to snoop with usbmon. > > Because a device is not bound by a driver does not mean it will not show > up in the devices file, that file shows all USB devices in the system. > > And as such, usbmon should let you look at it, but if no driver is > talking to it, no data will be sent. > > > My question is: How could I tweak the hotplug/HID system to force it to > > take in account this device, even if it doesn't announces itself as a > > regular human interface device ? > > I wouldn't recommend it, unless it's a real HID device. Probably just > write an input driver for it instead, once you figure out the data > protocol being used. > > good luck, > > greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
