From: Jens Axboe <axboe@suse.de>
To: Mark Lord <liml@rtr.ca>
Cc: albertl@mail.com, Jeff Garzik <jgarzik@pobox.com>,
Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata-dev: recognize WRITE_MULTI_FUA_EXT for r/w multiple
Date: Fri, 3 Mar 2006 15:28:23 +0100 [thread overview]
Message-ID: <20060303142823.GQ4329@suse.de> (raw)
In-Reply-To: <4408521B.9000905@rtr.ca>
On Fri, Mar 03 2006, Mark Lord wrote:
> Albert Lee wrote:
> >Jeff,
> >
> >Changes:
> >Recognize ATA_CMD_WRITE_MULTI_FUA_EXT as r/w multiple commands.
>
> This one will require exhaustive testing on various controllers.
> There are quite a few PIO boards with FIFOs that "recognize"
> opcodes for READs and WRITEs. And practically all of them predate
> any concept of FUA commands.
>
> Very VERY risky.
Which is why it's so annoying and seemingly idiotic that t13 keeps
making up new opcodes for the exact same thing instead of allowing
options bits.
--
Jens Axboe
next prev parent reply other threads:[~2006-03-03 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 2:34 [PATCH] libata-dev: recognize WRITE_MULTI_FUA_EXT for r/w multiple Albert Lee
2006-03-03 14:26 ` Mark Lord
2006-03-03 14:28 ` Jens Axboe [this message]
2006-03-03 17:22 ` 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=20060303142823.GQ4329@suse.de \
--to=axboe@suse.de \
--cc=albertl@mail.com \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
/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).