Re: How should we handle bogus bInterval descriptor values?
Alan Stern <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 7 May 2007, Oliver Neukum wrote: > Am Montag, 7. Mai 2007 18:06 schrieb Alan Stern: > > > Possibilities: > > > > Unilaterally change the 0 to something reasonable -- but what? > > Leave it to the drivers. I don't like that because there are lots of drivers -- but there's only one usbcore. > > Declare the descriptor illegal and log a warning message. > > > > Any other suggestions? > > WARN_ON() for using 0. Just doing a WARN_ON() won't solve the problem. We actually have to do something to prevent the 0 value from ever being used. 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