From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, hancockr@shaw.ca
Subject: Re: [patch 07/30] libata: add NCQ blacklist entries from Silicon Image Windows driver
Date: Tue, 06 Mar 2007 06:45:35 -0500 [thread overview]
Message-ID: <45ED545F.2070402@garzik.org> (raw)
In-Reply-To: <200703061037.l26AbtT4019472@shell0.pdx.osdl.net>
akpm@linux-foundation.org wrote:
> From: Robert Hancock <hancockr@shaw.ca>
>
> This patch adds in some NCQ blacklist entries taken from the Silicon Image
> Windows drivers' .inf files for the 3124 and 3132 controllers. These
> entries were marked as ""DisableSataQueueing". Assume these are in their
> blacklist for a reason and disable NCQ on these drives.
>
> Signed-off-by: Robert Hancock <hancockr@shaw.ca>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/ata/libata-core.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff -puN drivers/ata/libata-core.c~libata-add-ncq-blacklist-entries-from-silicon-image-windows drivers/ata/libata-core.c
> --- a/drivers/ata/libata-core.c~libata-add-ncq-blacklist-entries-from-silicon-image-windows
> +++ a/drivers/ata/libata-core.c
> @@ -3368,6 +3368,13 @@ static const struct ata_blacklist_entry
>
> /* Devices with NCQ limits */
>
> + /* The following blacklist entries are taken from the Windows
> + driver .inf files for the Silicon Image 3124 and 3132. */
> + { "Maxtor 7B250S0", "BANC1B70", ATA_HORKAGE_NONCQ, },
> + { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, },
> + { "HTS541080G9SA00", "MB4OC60D", ATA_HORKAGE_NONCQ, },
> + { "HTS541010G9SA00", "MBZOC60D", ATA_HORKAGE_NONCQ, },
Already discussed: drop the HTS* entries, leaving only the Maxtor, and
I'll apply it
prev parent reply other threads:[~2007-03-06 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:37 [patch 07/30] libata: add NCQ blacklist entries from Silicon Image Windows driver akpm
2007-03-06 11:45 ` Jeff Garzik [this message]
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=45ED545F.2070402@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.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).