On Thu, 26 Apr 2007, Bret Towe wrote: > For some time now at a place I work at we have been using some Unitech > MS-180 barcode scanners todo logins the work around we had in place > basicly was using a 2.4 kernel on the thin clients doing the logins > since 2.4 worked with them 2.6 had some issue and I had posted here > asking for help and got some suggestions on how to precede, between the > work around working and me not knowing the USB/HID code any I had > ignored the issue.
Hi Bret, do I get your mail right that 2.4 works fine with the hid driver, but to make things working in 2.6 you have to use usbkbd driver? If so, we certainly need to fix this regression. usbkbd should not be used in production. > Checking the difference between the working older scanners and newer > broken I saw the following via usbmon the below is from a scan of the > same barcode from 2 scanners. all the C lines on the broken start with > 01 and seem to be shifted compaired to the working > working: > ffff810035c5ea40 536368059 C Ii:005:01 0 8 = 02000000 00000000 > ffff810035c5ea40 536368088 S Ii:005:01 -115 8 < > ffff810035c5ea40 536376058 C Ii:005:01 0 8 = 02001800 00000000 > ffff810035c5ea40 536376080 S Ii:005:01 -115 8 < > ffff810035c5ea40 536384057 C Ii:005:01 0 8 = 00000000 00000000 > ffff810035c5ea40 536384075 S Ii:005:01 -115 8 < > broken: > ffff810035c5e980 593493403 C Ii:006:01 0 8 = 01020000 00000000 > ffff810035c5e980 593493417 S Ii:006:01 -115 8 < > ffff810035c5e980 593501397 C Ii:006:01 0 8 = 01020018 00000000 > ffff810035c5e980 593501413 S Ii:006:01 -115 8 < > ffff810035c5e980 593509400 C Ii:006:01 0 8 = 01000000 00000000 > ffff810035c5e980 593509419 S Ii:006:01 -115 8 < This by itself doesn't necessairly mean that it's broken, the report descriptor for the two devices might be different, and therefore the individual bytes in the URB should have different meaning. > also I do have usbmon logs of one of the scanners being plugged in with > just hid loaded and with usbkbd loaded and unplugging again If wanted I > can attach or upload somewhere from what I gather usbkbd should not have > to be relied on unless your doing embedded work or inital boot > requirements? Exactly. We certainly have to make this supported by the hid driver if possible. What kernel version do you use? Could you please grab any recent one (2.6.21 is preferred), and compile the kernel with CONFIG_HID_DEBUG option enabled? (you'll find it under Device Drivers -> HID devices -> HID debugging support in menuconfig), and post the output corresponsing both to the time the device is connected to the system and also when the data is being processed? Thanks, -- Jiri Kosina ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
