From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Eric D. Mudama" <edmudama@gmail.com>,
Tejun Heo <htejun@gmail.com>,
Nicolas Mailhot <nicolas.mailhot@gmail.com>,
Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: Re: FUA and 311x (was Re: LibPATA code issues / 2.6.15.4)
Date: Thu, 2 Mar 2006 08:22:38 +0100 [thread overview]
Message-ID: <20060302072237.GS4816@suse.de> (raw)
In-Reply-To: <4406512A.9080708@pobox.com>
On Wed, Mar 01 2006, Jeff Garzik wrote:
> Jeff Garzik wrote:
> >For libata, I think an ATA_FLAG_NO_FUA would be appropriate for
> >situations like this... assume FUA is supported in the controller, and
> >set a flag where it is not. Most chips will support FUA, either by
> >design or by sheer luck. The ones that do not support FUA are the
> >controllers that snoop the ATA command opcode, and internally choose the
> >protocol based on that opcode. For such hardware, unknown opcodes will
> >inevitably cause problems.
>
> This also begs the question... what controller was being used, when the
> single Maxtor device listed in the blacklist was added? Perhaps it was
> a problem with the controller, not the device.
Yeah which explains it a lot better as well... The FUA drive problem
never made much sense to me.
--
Jens Axboe
next prev parent reply other threads:[~2006-03-02 7:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 19:00 LibPATA code issues / 2.6.15.4 Nicolas Mailhot
2006-03-01 19:22 ` Mark Lord
2006-03-01 23:12 ` Nicolas Mailhot
2006-03-01 23:31 ` Jeff Garzik
2006-03-02 1:19 ` Eric D. Mudama
2006-03-02 1:39 ` Eric D. Mudama
2006-03-02 1:56 ` FUA and 311x (was Re: LibPATA code issues / 2.6.15.4) Jeff Garzik
2006-03-02 1:58 ` Jeff Garzik
2006-03-02 2:20 ` Eric D. Mudama
2006-03-02 2:46 ` Jeff Garzik
2006-03-02 3:00 ` Eric D. Mudama
2006-03-02 3:06 ` Jeff Garzik
2006-03-02 3:13 ` Tejun Heo
2006-03-02 3:16 ` Mark Lord
2006-03-02 3:18 ` Jeff Garzik
2006-03-02 6:23 ` Eric D. Mudama
2006-03-02 9:00 ` Sander
2006-03-02 11:52 ` Jeff Garzik
2006-03-02 8:57 ` Sander
2006-03-03 0:34 ` Mark Lord
2006-03-02 16:12 ` Nicolas Mailhot
2006-03-02 16:07 ` Nicolas Mailhot
2006-03-02 16:03 ` Nicolas Mailhot
2006-03-02 16:05 ` Nicolas Mailhot
2006-03-02 7:22 ` Jens Axboe [this message]
2006-03-02 15:59 ` Nicolas Mailhot
2006-03-02 16:37 ` 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=20060302072237.GS4816@suse.de \
--to=axboe@suse.de \
--cc=Carlos.Pardo@siliconimage.com \
--cc=edmudama@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.mailhot@gmail.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).