summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorAlan Cox <alan@lxorguk.ukuu.org.uk>2006-09-12 16:55:12 +0100
committerJeff Garzik <jeff@garzik.org>2006-09-19 01:58:00 -0400
commit93590859884784520a1850767f86296abc2cdc6d (patch)
tree7465312f962467d8af3b24dd0f7510ea7113e010 /include/linux
parent4a3381feb823e06c8e2da7e283c17b0b6fdbddcf (diff)
downloadblackbird-op-linux-93590859884784520a1850767f86296abc2cdc6d.tar.gz
blackbird-op-linux-93590859884784520a1850767f86296abc2cdc6d.zip
[PATCH] libata: improve handling of diagostic fail (and hardware that misreports it)
Our ATA probe code checks that a device is not reporting a diagnostic failure during start up. Unfortunately at least one device seems to like doing this - the Gigabyte iRAM. This is only done for the master right now (which is fine for the iRAM as it is SATA), as with PATA some combinations of ATAPI device seem to fool the check into seeing a drive that isn't there if it is applied to the slave. Signed-off-by: Alan Cox <alan@redhat.com> Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/libata.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/linux/libata.h b/include/linux/libata.h
index ff67e7524fe9..1ef3d3901b47 100644
--- a/include/linux/libata.h
+++ b/include/linux/libata.h
@@ -289,6 +289,11 @@ enum {
* most devices.
*/
ATA_SPINUP_WAIT = 8000,
+
+ /* Horkage types. May be set by libata or controller on drives
+ (some horkage may be drive/controller pair dependant */
+
+ ATA_HORKAGE_DIAGNOSTIC = (1 << 0), /* Failed boot diag */
};
enum hsm_task_states {
@@ -476,6 +481,7 @@ struct ata_device {
/* error history */
struct ata_ering ering;
+ unsigned int horkage; /* List of broken features */
};
/* Offset into struct ata_device. Fields above it are maintained
OpenPOWER on IntegriCloud