On Tue, 23 Jun 2009, Frans Pop wrote: > > There is no problem. What you thought was a discrepancy really wasn't. > > Run your new script and you'll see. It only _looked_ like a > > discrepancy because you were comparing a decimal value to a hex value. > > Yes of course, but what I mean is that this decision means that still > bMaxPacketSize0 will be binary while wMaxPacketSize is hex in sysfs. > Having two variables that essentially contain the same info in a differing > format seems illogical to me. The USB standard itself treats ep0 differently from the other endpoints. The encoding of values in the bMaxPacketSize0 field is different from the encoding in wMaxPacketSize. So don't worry about it. > It also means we cannot display the multiplier for ep00 (we dropped its E: > line after all), while we do display it for the other end points. ep0 never has a multiplier (it is always 1). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
