Hi,I'm not quite sure if this is the right way to post a message to this list and/or to request a patch-review/-inclusion.
Well, I have problems with the mouse mentioned in the subject. It is neither recognized in the normal boot-up nor when re-plugging it after the boot-up. Turning on USB_DEBUG has shown: "usbd_get_string: getting string failed, using 0". I have searched your list and the net, but without any success. Ok, there was a hint about commenting out the code, but I think this is not the way it is ment to be. So I decided to have a look into the sources under /usr/src/sys/dev/usb. In fact, there is already a Logitech iFeel Mouse under usbdevs, but with a different device id. The listed device is 0xc030 whilst mine is 0xc032. So I added a new entry "product LOGITECH UN53B 0xc032 iFeel MouseMan". Actually this did not solve the problem of failing recognition of the device :-) So I took a closer look on usbdi.c::usbd_get_string() which is the point of failure and found "if (dev->quirks->uq_flags & UQ_NO_STRINGS)" which in turn checks the device for being unable to provide the strings usbdi.c::usbd_get_string() wants to extract. So the next step was to add the newly created usbdevs entry to usb_quirks.c with UQ_NO_STRINGS as the corresponding quirk. Now the mouse is shown in usbdevs, works fine in moused and under Xorg. It is successfully recognized as /dev/ums0 4-button mouse with scroll wheel.
Attached there are the patches of the changes I did. Hopefully they will find their way into the tree, since there seem to be a lot of people struggling with that (mouse') problem.
Btw. system is: AthlonXP on VIAKT400A+ (VT82xxxxx UHCI USB) running 7.0-CURRENT-200607.
Best regards,
Heiko
ifeel_mouseman_usb_quirks.c.patch
Description: Binary data
ifeel_mouseman_usbdevs.patch
Description: Binary data
PGP.sig
Description: This is a digitally signed message part
