From: Mark Lord <liml@rtr.ca>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Vitaliyi <imgrey@gmail.com>,
Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: add support for READ/WRITE LONG
Date: Fri, 16 Mar 2007 10:42:28 -0400 [thread overview]
Message-ID: <45FAACD4.6000709@rtr.ca> (raw)
In-Reply-To: <45FAAACE.6000503@ru.mvista.com>
Sergei Shtylyov wrote:
> Hello.
>
> Mark Lord wrote:
..
>>> Again, ata_data_xfer() doesn't seem capable of performing ECC
>>> read/writes
>>> -- the ECC bytes must be transferred in 8-bit mode, AFAIR.
>>> ata_data_xfer()
>>> can oinly do that for optionally trailing odd byte.
>
>> I have no idea what that was all about. Care to explain again?
>
> Care to read the standards? :-/
>
>> RWLONG transfer the ECC info 8-bits at a time, using 16-bit words
>> to do so, no different from normal. ???
>
> From ATA-1:
>
> "The transfer of the vendor specific bytes shall be one byte at a
> time over bits DD0-7 only (8-bits wide)."
> Yes, I said that already. 8-bits at a time, but using 16-bit transfers.
> Kinda like it says here, in ATA-3 section 7.16:
> The transfer of the vendor specifc bytes shall be 16 bit transfers
> with the vendor specific byte in bits 7 through 0. Bits 15 through 8
> shall be ignored by the host.
But if we really want to be 100% compliant, we could consider dropping
to PIO0 for the command. Not worth it, though, as in practice this is
not necessary, and it would mess up libata far more than is worthwhile
for this effort.
Cheers
next prev parent reply other threads:[~2007-03-16 14:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3aac340703102322p362998b9labedc13503702d2b@mail.gmail.com>
2007-03-12 14:47 ` libata extension Mark Lord
[not found] ` <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>
2007-03-12 19:08 ` [PATCH] libata: add support for READ/WRITE LONG Mark Lord
2007-03-12 19:10 ` Mark Lord
2007-03-12 22:13 ` Alan Cox
2007-03-12 22:23 ` Mark Lord
2007-03-13 0:08 ` Alan Cox
2007-03-12 23:40 ` Mark Lord
2007-03-13 6:40 ` Tejun Heo
2007-03-13 10:46 ` Ric Wheeler
2007-03-16 12:28 ` Mark Lord
2007-03-16 14:02 ` Sergei Shtylyov
2007-03-16 14:22 ` Mark Lord
2007-03-16 14:33 ` Sergei Shtylyov
2007-03-16 14:42 ` Mark Lord [this message]
2007-03-16 14:43 ` Mark Lord
2007-03-16 14:58 ` Sergei Shtylyov
2007-03-16 15:07 ` Mark Lord
2007-03-16 15:23 ` Sergei Shtylyov
2007-03-16 15:32 ` Mark Lord
2007-03-16 17:08 ` Alan Cox
2007-03-16 18:54 ` Jeff Garzik
2007-03-16 20:16 ` Mark Lord
2007-03-16 20:38 ` Jeff Garzik
2007-03-16 21:05 ` Sergei Shtylyov
2007-03-16 21:09 ` Bartlomiej Zolnierkiewicz
2007-03-16 21:21 ` Mark Lord
2007-03-16 21:40 ` Bartlomiej Zolnierkiewicz
2007-04-04 6:20 ` Jeff Garzik
2007-03-16 15:15 ` Alan Cox
2007-03-16 14:16 ` Sergei Shtylyov
2007-03-16 15:01 ` Alan Cox
2007-03-16 14:15 ` Mark Lord
2007-03-16 14:23 ` Sergei Shtylyov
2007-03-16 14:33 ` Mark Lord
2007-03-16 15:23 ` Alan Cox
[not found] ` <3aac340703121007q35c7acf7t648e0ed7608be04d@mail.gmail.com>
[not found] ` <200703122106.39669.bzolnier@gmail.com>
2007-03-13 2:36 ` Fwd: libata extension Vitaliyi
2007-03-13 11:23 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FAACD4.6000709@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=imgrey@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).