This message is from the T13 list server.
Yes, it's all a conspiracy. Get off your soapbox please.
Where is the data integrity issues?? There is no cover up.
If there is a CRC error on a command FIS, it is retried. If it continues
to fail, the host obviously knows about it, nothing is 'hidden'.
If a bus error occurs during data transfer, the device reports a CRC error
to the host whether it is DMA, PIO, or whatever. The only issue is the
last data packet on a PIO transfer. The device cannot report the error to
the host since status goes out before the data. But, the host still knows
about it because the R_ERR is still seen by the host. Again nothing is
hidden.
Unlike PATA, SATA has CRC checking on all transfers. Likewise, errors are
detected on both sides of the cable. Nothing is ever hidden. PATA does
not have this protection. Especially for PIO transfers.
If a PATA cable has signal integrity issues, PIO data transfers will be
corrupt and no reporting can be detected or reported. How can this
possibly be more robust than SATA?
If there are data integrity issues with SATA, it has never, I repeat, never
been reported back to device manufacturers.
Please discontinue your 'secret society' comments and slanderous assault on
an interface just because you personally were not invited to attend. These
types of comments belong on a Blog site, not this forum.
My comments are mine personally and do not reflect the company I work for.
Thank you,
Bob
Hale Landis
<[EMAIL PROTECTED]
m> To
Sent by: T13 List Server <[email protected]>
[EMAIL PROTECTED] cc
rg
No Phone Info Subject
Available Re: [t13] SATA PIO data-out with
Data FIS error
12/15/2005 03:59
PM
Please respond to
Hale Landis
<[EMAIL PROTECTED]
i.com>
This message is from the T13 list server.
Dees, Brian M wrote:
> This message is from the T13 list server.
> In the Error register, the ABRT and ICRC bits should be set per updates
> that are included in latest drafts of ATA8-ACS. Updates have been made
> to the Interface CRC description to allow ICRC reporting for MWDMA and
> PIO, and additional notes have been added to the Error Outputs for all
> PIO data-in and PIO data-out commands to allow this.
Come on now... This is no time to be quiet about the serious data
integrity problems that SATA has that no one has wanted to talk about
for 2+ years.
Now it the time to publish the minutes of the SATAIO meetings where this
issue has been discussed and explain why it has taken so long for the
issue to be addressed. And the SATAIO membership owes an explaination to
everyone that has purchased SATA equipment as to the serverity of this
issue and what can be done about it - especially those that have SATA
host controllers that are emulating a PATA host controller and may be
running software (BIOS, OS, etc) that are unaware that the actual
hardware is SATA.
At this point I don't think SATAIO can continue to cover up this issue.
Hale
--
++ Hale Landis ++ www.ata-atapi.com ++
