On Tue, 17 Jan 2006, Brian Stumm wrote: > Vojtech Pavlik wrote: > > > On Tue, Jan 17, 2006 at 10:32:12AM -0800, Brian Stumm wrote: > > > > > I assume thats the MxPS value from /proc/bus/usb/devices??? If so I think > > > its 5 for > > > mouse and 8 for keyboard. > > > > > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 > > > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > > P: Vendor=060b ProdID=0541 Rev= 1.01 > > > C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA > > > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid > > > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms > > > I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid > > > E: Ad=82(I) Atr=03(Int.) MxPS= 5 Ivl=10ms > > > > Wow. I've never seen a maxpacketsize other than a power of two. That > > seems like a bug in the device descriptor, that might cause problems > > elsewhere in the stack. > > Snoopy/Windows reports the same (http://churchoftux.com/snoopy/ contains > sniffer logs): > Interface[0]: Pipes[0] : MaximumPacketSize = 0x0005 > > How might I further debug or where do I look to see how this strange packet > size is > affecting things?
It's not affecting anything. (It works fine with 5-byte packets under Windows, for instance.) If the device were to send back a packet containing more than 5 bytes you'd be in trouble. As things stand, however, it's not sending back anything at all. On the whole, it's hard to say which is worse... :-( Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
