Allen Martin wrote:
At least for NVIDIA controllers, loading the AHCI driver when the BIOS
is set to IDE mode is not recommended by NVIDIA. Any AHCI workarounds
in the BIOS are likely to be disabled when set to IDE mode. In practice
What workarounds, if any, are needed?
We need those in the driver not BIOS anyway, in order to fully support
suspend/resume and host controller reset during runtime operation.
we don't expect to see a lot of users running an AHCI controller in IDE
mode unless they have explicitly disabled AHCI from the BIOS or the
system builder has some specific reason for shipping IDE mode by default
(like support for some legacy DOS or Win9x tools)
That's the situation we run into the most: the system is in IDE mode
not because AHCI doesn't work, but for legacy compatibility. We even
run into cases (MacBook, Dell servers) where the user is never offered
the option to turn on AHCI, even though the silicon supports it.
As such, the user winds up being forced to into the inferior mode for no
reason related to their own setup (since they are obviously running Linux).
In Linux at least, we have a bunch of open sata_nv issues, so forcing
users' interface into AHCI mode as a default future policy seems like
the most stable choice on NVIDIA AHCI platforms.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
