Dear Alan,
>> After that see the Table 5-1. Low-speed Control Transfer Limits.
>> Even though there are a total of 43 bytes to be transferred, I
observe
>> that data payload is less that 8 bytes some times which is against
the
>> above rule in 5.5.3.
>
>Where do you get that 43 from?
I got it through (Max transfers + Bytes remaining).
I guess Max
> The table has 4 rows. The first row
>illustrates what happens when 1 byte is to be transferred. The second
row
>illustrates what happens when 2 bytes are to be transferred. The third
>row illustrates what happens when 4 bytes are to be transferred. And
the
>fourth row illustrates what happens when 8 bytes are to be transferred.
Thanks for the explanation.
But, I did not get how MAX Transfers vary?
And what does "bytes remaining" mean?
And I find two ways of addressing like transfers and transactions. I
understand them as follows. Please correct me in case I am wrong.
I guess 1 transfer will involve multiple transactions. Generally it will
be 3 i.e. setup, data and handshake. If the data to be transferred is
more the transaction count will increase.
I guess,
1 transfer = (1 setup transaction + 1 or more data transaction +
1 handshake transaction)
>In each case there is only one data packet. Since there is only one,
it
>is the last one. Hence it is free to carry fewer than 8 bytes.
Ok, that is clear.
Thanks of the help.
Regards,
Mukund Jampala
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
