Bug#248855: Useful clues for non-working USB keyboard on SunBlade 150 / sparc64
> Attached are two alternative patches for usb-kbd.c (both untested!):
> 1) The evidence seems to support the theory that usb keyboards can be
> safely identified by CLs=03, Sub=01, Prot=01.
> This patch cleans up the existing code based on that theory.
I checked a completely different machine with a USB keyboard, and
got this from /proc/bus/devices/usb. (Dell precision 380 desktop,
i386 arch.)
<snip>
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc=118/900 us (13%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff60
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=413c ProdID=2003 Rev= 1.00
S: Manufacturer=Dell
S: Product=Dell USB Keyboard
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbkbd
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=24ms
</snip>
Based on the last "I:" line, the theory is holding up thus far.
The only things I can see to worry about:
- are there cases where Sub!=01. (Boot Interface Subclass)?
- are there keyboards where Prot!=01 (keyboard Interface Protocol)?
I'm no usb expert either.
I was wondering if discover plays a role here. I noticed a couple
of "unknown" items in pci.list that match pci ids in my SB100.
The USB controller entry seems correct however
108e1103 usb usb-ohci RIO USB
Cheers
Vince
Reply to: