diff options
author | Jeff Garzik <jeff@garzik.org> | 2012-08-17 13:36:59 -0400 |
---|---|---|
committer | Jeff Garzik <jgarzik@redhat.com> | 2012-08-17 13:36:59 -0400 |
commit | 04d0f1b84927169cdaa4e3a24da768a9fd9aca6f (patch) | |
tree | e13bb1541b1e13398be005bf405067951dc8a204 /drivers/ata/pata_macio.c | |
parent | ebd600281566ab40fb2e3004af7eacb3375626d1 (diff) | |
download | linux-04d0f1b84927169cdaa4e3a24da768a9fd9aca6f.tar.gz |
[libata] new quirk, lift bridge limits for Buffalo DriveStation Quattro
Michael Eitelwein writes: I have an external SATA drive that was slowed down by bridge limits. I found a solution in a thread on this list posted in 2008: It introduces whitelist entries in libata-core.c for devices with well working bridges (e.g. email on Fri, 31 Oct 2008 01:45:27 -0400). I added my device to this whitelist in a custom built kernel and it works fine for weeks now. How can I have this device added on the whitelist within the official kernel? Is this whitelist mechanism still supported or is there a smarter way to achieve whitelisting? I added the following whitelist entry for my Buffalo DriveStation Quattro "BUFFALO HD-QSU2/R5": /* Devices that do not need bridging limits applied */ { "MTRON MSP-SATA*", NULL, ATA_HORKAGE_BRIDGE_OK, }, { "BUFFALO HD-QSU2/R5", NULL, ATA_HORKAGE_BRIDGE_OK, }, Reported-by: Michael Eitelwein <michael@eitelwein.net> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'drivers/ata/pata_macio.c')
0 files changed, 0 insertions, 0 deletions