The patch titled
libata: add NCQ blacklist entries from Silicon Image Windows driver
has been removed from the -mm tree. Its filename was
libata-add-ncq-blacklist-entries-from-silicon-image-windows.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
Subject: libata: add NCQ blacklist entries from Silicon Image Windows driver
From: Robert Hancock <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
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, },
+
/* End Marker */
{ }
};
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
sata_nv-add-back-some-verbosity-into-adma-error_handler.patch
libata-warn-if-speed-limited-due-to-40-wire-cable-v2.patch
libata-add-ncq-blacklist-entries-from-silicon-image-windows.patch
sata_nv-dont-read-shadow-registers-when-in-adma-mode.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
