This message is from the T13 list server.

Forgot to send this one to the reflector (Sorry Pat)...

==================BEGIN FORWARDED MESSAGE==================
>To: "Pat LaVarre" <[EMAIL PROTECTED]>
>Date: Mon, 10 Dec 2001 21:15:59 -0700
>From: "Hale Landis" <[EMAIL PROTECTED]>
>Subject: Re: [t13] to Atapi from Usb: non-whole block residues

On Mon, 10 Dec 2001 13:48:39 -0700, Pat LaVarre wrote:
>Where in Ata/pi we have 16-bit data clocks, Usb has x8, x10,
>x20, x40, or x200 byte packets.

It doesn't matter what restrictions or capabilities existed on
the X side of an X-to-ATA/ATAPI bridge.  The bridge must follow
the ATA/ATAPI protocols on the ATA side and I assume it should
follow the X protocols on the X side.  Of course that means
snooping commands and command parameters, buffering data so that
things like the X packet protocols are not violated, etc.

When someone or some company takes on the task of designing an
X-to-Y bridge they have the responsibility to fully understand
both X and Y and make sure your bridge works properly on both X
and Y interfaces.

===================END FORWARDED MESSAGE===================


***  Hale Landis  *** [EMAIL PROTECTED] ***
*** Niwot, CO USA ***   www.ata-atapi.com   ***


Subscribe/Unsubscribe instructions can be found at www.t13.org.

Reply via email to