This message is from the T13 list server.
My experience is that such things are usually confusing - we have tried them before on other features. The bottom line problem here is that you are trying to modify the standard to catch problems that are due to people not implementing the standard (since when would any device expecting 512 bytes legitimately count 514 bytes as legal?). If this is the case, then fixing it with more standards work does not work (they will just screw that up as well). Better is usually an agreement from T13 on the correct interpretation (if needed) and a heads up for people testing for compliance. That should flush out bad designs out of the market much faster. Jim -----Original Message----- From: Pat LaVarre [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 04, 2001 12:43 PM To: [EMAIL PROTECTED] Subject: [t13] a fix for imprecise UDma residue? This message is from the T13 list server. Hey everyone: Anyone clueful want to nominate an xA1 IdentifyPacketDevice bit to fix this: to make SwDma/MwDma/UDma as capable of precise byte counts as Pio? If the bit is set, then the device promises, in the x03 StatusIn phase after some Dma data moved out, to set x1F5:1F4 to the bytes it received but did not request. For example, if the host sent 514 bytes but no matter than in Pio mode the device would only have requested 512 bytes, the device would set x1F5:1F4 = x00:02. If the host sent 8 bytes but in Pio mode the device only would have requested 7 bytes, the device would set x1F5:1F4 to x00:01. Good/ bad/ confused idea? Please comment. Thanks in advance. Pat LaVarre Subscribe/Unsubscribe instructions can be found at www.t13.org. Subscribe/Unsubscribe instructions can be found at www.t13.org.
