RE: [t13] residue after the fact - a performance disaster?

2001-12-10 Thread Mcgrath, Jim
This message is from the T13 list server. The problem is that in SCSI it involves a transition from DATA PHASE to MESSAGE PHASE. With the exception of a few messages that are always seen in a command (like IDENTIFY), most SCSI devices handle the message system in firmware, not hardware. This

RE: [t13] non-communication of non-whole-block residue

2001-12-10 Thread Mcgrath, Jim
This message is from the T13 list server. Pat, The problem I have is why X matters at all at the ATA/ATAPI level. There are two interfaces here - one is from bridge to host (I'll assume USB, but the principle applies elsewhere), the other is the bridge to the device (I'll assume ATAPI). If

RE: Fwd: Re: [t13] Register vs. data PIO timing

2001-12-10 Thread Mcgrath, Jim
This message is from the T13 list server. This makes sense, but both data and register tables have the same timings for the address setup times. So the design may be taking advantage of the stable address in data transfers, but we don't in the standard. Jim -Original Message- From:

RE: [t13] a fix for imprecise UDma residue?

2001-12-10 Thread Hale Landis
This message is from the T13 list server. On Mon, 10 Dec 2001 13:41:22 -0700, Pat LaVarre wrote: You only have one step further to go: all you have to add is your explanation of HOW the host and the target come to agree over how many bytes they jointly agreed to move. For an ATA command the

RE: [t13] a fix for imprecise UDma residue?

2001-12-10 Thread Hale Landis
This message is from the T13 list server. On Mon, 10 Dec 2001 20:49:19 -0700, Hale Landis wrote: Better fux those bridge devices that try to short cut this. Holy cow! Did I just create a new word by mistyping the word fix??? *** Hale Landis *** [EMAIL PROTECTED] *** *** Niwot, CO USA ***