From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Lord <lkml@rtr.ca>, "Eric D. Mudama" <edmudama@gmail.com>,
Jens Axboe <axboe@suse.de>, Tejun Heo <htejun@gmail.com>,
Nicolas Mailhot <nicolas.mailhot@gmail.com>,
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, 02 Mar 2006 19:34:25 -0500 [thread overview]
Message-ID: <44078F11.1010904@rtr.ca> (raw)
In-Reply-To: <44066400.6070503@pobox.com>
Jeff Garzik wrote:
> Mark Lord wrote:
>> Jeff Garzik wrote:
>> ..
>>
>>> Sounds like un-blacklisting the drive, and adding ATA_FLAG_NO_FUA is
>>> the way to go...
>>
>>
>> Might as well add sata_mv to that blacklist as well.
>
> Have you confirmed that it doesn't work with FUA?
Ooops. Defective memory here.
The Marvell documentation for the 6081/6041 does indeed state
that the FUA DMA commands *are* supported (queued or non-queued).
So it should be okay, at least for those two specific chips.
next prev parent reply other threads:[~2006-03-03 0:34 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 [this message]
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
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=44078F11.1010904@rtr.ca \
--to=liml@rtr.ca \
--cc=Carlos.Pardo@siliconimage.com \
--cc=axboe@suse.de \
--cc=edmudama@gmail.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.