Lines Matching refs:URB
30 to transfer the URB traffic between the client and the server. The client may
31 send two types of packets: the USBIP_CMD_SUBMIT to submit an URB, and
32 USBIP_CMD_UNLINK to unlink a previously submitted URB. The answers of the
236 USBIP_CMD_SUBMIT: Submit an URB
240 0 | 4 | 0x00000001 | command: Submit an URB
242 4 | 4 | | seqnum: the sequence number of the URB to submit
252 | | | URB transfer type, see below
268 0x30 | | | URB data. For ISO transfers the padding between
283 USBIP_RET_SUBMIT: Reply for submitting an URB
289 4 | 4 | | seqnum: URB sequence number
298 0x14 | 4 | | status: zero for successful URB transaction,
301 0x18 | 4 | n | actual_length: number of URB data bytes
313 0x30 | n | | URB data bytes. For ISO transfers the padding
316 USBIP_CMD_UNLINK: Unlink an URB
320 0 | 4 | 0x00000002 | command: URB unlink command
322 4 | 4 | | seqnum: URB sequence number to unlink: FIXME: is this so?
331 0x14 | 4 | | seqnum: the URB sequence number given previously
334 0x30 | n | | URB data bytes. For ISO transfers the padding
337 USBIP_RET_UNLINK: Reply for URB unlink
341 0 | 4 | 0x00000004 | command: reply for the URB unlink command
343 4 | 4 | | seqnum: the unlinked URB sequence number
353 | | | urb->status in the URB completition handler.
356 0x30 | n | | URB data bytes. For ISO transfers the padding