On Mon, May 17, 2004 at 10:23:34PM +0200, Oliver Neukum wrote:
> Am Montag, 17. Mai 2004 20:37 schrieb Alan Stern:
> > The basic idea is simple enough. ?When an URB has been successfully 
> > submitted it is owned by the USB core, not your driver. ?You may not 
> > modify it and probably shouldn't even read it until the completion 
> > handler is called.
> 
> Hm, that makes me wonder. Does urb->status make sense at all?

No, it really doesn't.

> Maybe we should simply pass the status as a third argument to the
> completion handler.

YES!

But that's a 2.7 thing, due to the fact we would have to change _every_
urb callback :(

Then you can move the status field to the hcd private portion of the urb
(or somewhere else that it's obvious that USB drivers shouldn't be
touching it.)

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to