How should we handle bogus bInterval descriptor values?

In this bug report, lsusb shows an HID device which has bInterval set to 0 
in its two Interrupt endpoint descriptors:

	http://bugzilla.kernel.org/show_bug.cgi?id=8432

Of course this confuses the USB drivers, causing a lot of problems.

What should we do about such things?  And where should we do it?  By the
time fill_interrupt_urb() has been called it's already too late, since the
code does

	urb->interval = 1 << (bInterval - 1);

which is undefined when bInterval is 0.

Possibilities:

	Unilaterally change the 0 to something reasonable -- but what?

	Declare the descriptor illegal and log a warning message.

Any other suggestions?

Alan Stern


-------------------------------------------------------------------------
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/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel