On return from this function call, which entries in the struct urb * urb can now be examined by the application?
struct urb {
struct list_head urb_list;
struct usb_device * dev;
unsigned int pipe;
int status;
unsigned int transfer_flags;
void * transfer_buffer;
dma_addr_t transfer_dma;
int transfer_buffer_length;
int actual_length;
unsigned char * setup_packet;
dma_addr_t setup_dma;
int start_frame;
int number_of_packets;
int interval;
int error_count;
int timeout;
void * context;
usb_complete_t complete;
struct usb_iso_packet_descriptor * iso_frame_desc;
};Can the linux kernel documentation be expanded to include: -
Required values that need to be filled into struct urb for the call to work.
Return values that can be read safely from the struct urb after the submit_urb call.
Which return values can only be read during the urb_complete callback.
It would be nice if one could be sure the urb->start_frame is valid after this call.
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.
Cheers James
------------------------------------------------------- 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
