[PATCH] libata: improve handling of diagostic fail (and hardware that misreports it)
commit93590859884784520a1850767f86296abc2cdc6d
authorAlan Cox <alan@lxorguk.ukuu.org.uk>
Tue, 12 Sep 2006 15:55:12 +0000 (12 16:55 +0100)
committerJeff Garzik <jeff@garzik.org>
Tue, 19 Sep 2006 05:58:00 +0000 (19 01:58 -0400)
tree7465312f962467d8af3b24dd0f7510ea7113e010
parent4a3381feb823e06c8e2da7e283c17b0b6fdbddcf
[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>
drivers/ata/libata-core.c
include/linux/libata.h