From: Michal Soltys <soltys@ziu.info>
To: linux-ide@vger.kernel.org
Subject: Question regarding FUA state
Date: Wed, 22 Jul 2009 21:06:26 +0200 [thread overview]
Message-ID: <4A676332.6080205@ziu.info> (raw)
What is the current state of fua ?
While peeking over older (mainly 2007ish) threads, there was some
discussion about it - whenever it should or shouldn't be enabled by
default, automatic blacklisting for certain controllers (some SiI 3xxx,
others ...).
http://marc.info/?l=git-commits-head&m=114110310308542&w=2
http://marc.info/?t=117125096400001&r=2&w=2
http://marc.info/?t=117193493900004&r=1&w=2
http://marc.info/?t=118243369000005&r=1&w=2
Current state is "disabled by default", but simple libata module
parameter can enable it. How safe is that these days, and if enabled,
will problematic chipsets be blacklisted automtically ? (I didn't find
anything in the sources suggesting it happens, but I didn't look too
thoroughly either).
How do the following chipsets handle it:
- ICH8R and newer ones
- ATI's SB700/SB800 ones
- JMB36x
- which (if any) SiI chipsets are ok
next reply other threads:[~2009-07-22 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:06 Michal Soltys [this message]
2009-07-23 6:06 ` Question regarding FUA state Robert Hancock
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=4A676332.6080205@ziu.info \
--to=soltys@ziu.info \
--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).