This message is from the T13 list server.
> > One byte count that matters > > is the count of bytes written or read that the OS reports to the app. > > ... > > Another byte count that matters > > is the count of bytes actually written or read. > > ... > > iocb x 12 0 0 0 FF 0 /i x1000 > > > > Now suppose the device under test > > makes x91 bytes of Inquiry data available. > > With an AtapiPio device we see the host copies in x91 bytes. > > With an AtapiDma device we see the host copies in x92 bytes. > "Mcgrath, Jim" <[EMAIL PROTECTED]> 01/03/02 02:04PM > Your latest covers the same ground we have already covered before. > ... this is incorrect. At the ATA interface level > you always see 92 bytes, whether it is PIO or DMA. > It is up to something else on the host If we can't agree something as plainly broken as this is a problem ... ... I give up. I don't know how to make a more clear demo that changing from AtapiPio to AtapiDma is not a transparent change. Byte counts moved and reported are the very stuff of which plug 'n play failures are made. I don't see how this can be in dispute. Does everyone out there really think we don't care precisely how many bytes the host copies per command? Really??? > Basically, can you provide data that shows an actual problem here? I thought I had, repeatedly in many variations, sorry. Thanks for reading and for trying so long to talk. Curious that we can so persistently fail to communicate. Pat LaVarre Subscribe/Unsubscribe instructions can be found at www.t13.org.
