int usb_submit_urb (struct urb * urb, int mem_flags);
On return from this function call, which entries in the struct urb * urb can now be examined by the application?
struct urb { int start_frame;
I think the only one that changes validity at that time is start_frame. As documented with "struct urb".
};
Can the linux kernel documentation be expanded to include: -
Required values that need to be filled into struct urb for the call to work.
If you find anything that's not documented as being needed, let us know. Check both the "submit_urb" and the "struct urb" docs.
Return values that can be read safely from the struct urb after the submit_urb call.
start_frame.
Which return values can only be read during the urb_complete callback.
The only value documented as visible before complete() is the start_frame...
It would be nice if one could be sure the urb->start_frame is valid after this call.
The docs say you can be sure of that for any reserved-bandwidth transfer.
The kernel docs have a nice section on what values to give the "int mem_flags" argument, but next to nothing for the "strub urb *urb" argument.
Except as part of the "struct urb" documentation? :)
- Dave
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
