> From: [EMAIL PROTECTED] > Date: Tue, 21 May 2002 18:37:08 +0200 (MEST)
> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=05e3 ProdID=000a Rev= 0.00 > C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr= 48mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=8ms > I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) > E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=8ms > I: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=(none) > E: Ad=82(I) Atr=03(Int.) MxPS= 3 Ivl=8ms Hmmm.... > A USB keyboard that again connects to a (non-USB!) mouse. That's fine, I've got a bunch of those. Dell sent me some to make them working. I also bought one for myself. > The routine drivers/usb/input/hid-core.c:hid_init_reports() > submits a control usb via hid_submit_report(). > Then, a few lines down, it submits a control usb via usb_control_msg(). > > It is this couple that usb-uhci-hcd.c:uhci_urb_enqueue() complains > about saying "propably device driver bug...". IIRC, hid_submit_report submits an interrupt URB, not control. So it should be only one control when it sets report bases, etc. Please by all means make sure you are not using usbkbd and its mouse equivalent. -- Pete _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
