On Wed, 15 Jan 2003, oliverthered wrote: >Oh what fun......
yes, hurray for the usb spec writers... ;-) >I'll make a patch to fit the specification. let's agree on where to put it first; if it goes into the core (either generic hcd, or uhci/ohci/ehci) then the conversion only has to be done once (or maybe once per HCD). If it must be done by all drivers, then surely it will have to be done in more than one place... If the HCDs expect a bInterval value, then no conversion is needed from drivers nor generic hcd. I think since uhci-hcd and ohci-hcd handle 1.1 (low and full) only, and ehci-hcd handles highspeed only, it would be easiest to handle conversion in the HCDs themselves... -- 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
