[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL-cBk1L8dgAtP2hMwkL2B-cU76mKaaWib=QVbVKei2DaoB3Dw@mail.gmail.com>
Date: Mon, 4 Jul 2011 11:11:01 +0800
From: David Chang <dchang@...ell.com>
To: Németh Márton <nm127@...email.hu>
Cc: Greg KH <greg@...ah.com>, Matthew Wilcox <matthew@....cx>,
Max Vozeler <max@...eler.com>, Matt Mooney <mfm@...eddisk.com>,
Joe Perches <joe@...ches.com>, linux-usb@...r.kernel.org,
usbip-devel@...ts.sourceforge.net, devel@...verdev.osuosl.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH, RFC] USBIP protocol documentation
Hi Németh,
2011/6/29 David Chang <dchang@...ell.com>:
> Hi,
>
> Thanks for your great effort.
> Just a little comment on UNLINK pdu size.
>
> 2011/6/28 Németh Márton <nm127@...email.hu>:
>> From: Márton Németh <nm127@...email.hu>
>>
>> USBIP v1.0.0 protocol documentation.
>>
>> Signed-off-by: Márton Németh <nm127@...email.hu>
>> ---
>> +USBIP_CMD_UNLINK: Unlink an URB
>> +
>> + Offset | Length | Value | Meaning
>> +-----------+--------+------------+---------------------------------------------------
>> + 0 | 4 | 0x00000003 | command: URB unlink command
>> +-----------+--------+------------+---------------------------------------------------
>> + 4 | 4 | | seqnum: URB sequence number to unlink: FIXME: is this so?
>> +-----------+--------+------------+---------------------------------------------------
>> + 8 | 4 | | devid
>> +-----------+--------+------------+---------------------------------------------------
>> + 0xC | 4 | | direction: 0: USBIP_DIR_IN
>> + | | | 1: USBIP_DIR_OUT
>> +-----------+--------+------------+---------------------------------------------------
>> + 0x10 | 4 | | ep: endpoint number: zero
>> +-----------+--------+------------+---------------------------------------------------
>> + 0x14 | 4 | | seqnum: the URB sequence number given previously
>> + | | | at USBIP_CMD_SUBMIT.seqnum field
-----------+--------+------------+---------------------------------------------------
0x30 | n | | URB data bytes. For ISO
transfers the padding
| | | between each ISO
packets is not transmitted.
>> +
>> +USBIP_RET_UNLINK: Reply for URB unlink
>> +
>> + Offset | Length | Value | Meaning
>> +-----------+--------+------------+---------------------------------------------------
>> + 0 | 4 | 0x00000004 | command: reply for the URB unlink command
>> +-----------+--------+------------+---------------------------------------------------
>> + 4 | 4 | | seqnum: the unlinked URB sequence number
>> +-----------+--------+------------+---------------------------------------------------
>> + 8 | 4 | | devid
>> +-----------+--------+------------+---------------------------------------------------
>> + 0xC | 4 | | direction: 0: USBIP_DIR_IN
>> + | | | 1: USBIP_DIR_OUT
>> +-----------+--------+------------+---------------------------------------------------
>> + 0x10 | 4 | | ep: endpoint number
>> +-----------+--------+------------+---------------------------------------------------
>> + 0x14 | 4 | | status: This is the value contained in the
>> + | | | urb->status in the URB completition handler.
>> + | | | FIXME: a better explanation needed.
-----------+--------+------------+---------------------------------------------------
0x30 | n | | URB data bytes. For ISO
transfers the padding
| | | between each ISO
packets is not transmitted.
Would you add this field into your path or should I send another patch
to add it?
Thanks.
Regards,
David Chang
>
> Regards,
> David Chang
>
>>
>> _______________________________________________
>> devel mailing list
>> devel@...uxdriverproject.org
>> http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists