On Wed, 15 Jan 2003, David Brownell wrote:
>
>> Hmm, so should the conversion from bInterval to ms-interval happen in the
>> driver, or in the core? It seems to me that it would be better to handle
>> that conversion in the core...?
>
>We had that discussion last summer, and the resolution
>was that fill_int_urb() does it ... ISO drivers don't
>have such a utility to call.
mmm, that's too bad, it seems unfortunate to duplicate that conversion in
all iso drivers (and int drivers that don't use fill_int_urb)...
Wouldn't it make sense to have a conversion function in usb.c,
something like:
inline int bInterval_to_ms(unsigned char bInterval, int speed, int isoc)
{
if (USB_SPEED_HIGH == speed)
return (2^(bInterval-1)) * 125;
else if (isoc)
return (2^(bInterval-1));
else
return bInterval;
}
--
Dan Streetman
[EMAIL PROTECTED]
---------------------
186,272 miles per second:
It isn't just a good idea, it's the law!
-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate
is essential in establishing user confidence by providing assurance of
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
