> What I'm worred about is SMI traps implemented in the SBIOS for AHCI > workarounds that may be disabled when in IDE mode. For Nvidia devices those would only be present if there were problems with the AHCI hardware right, which would mean you could simply tell us what workarounds to implement. > I believe most of the issues with sata_nv have been due to lack of > documentation of ADMA and swNCQ. The NVIDA AHCI controllers that I am glad Nvidia accept this point. It would be nice to see it fixed. > I'm with you that AHCI mode is superior and should be used whenever > possible, but it probably comes as no suprise that almost all the > hardware/BIOS testing is done with Windows, and operating the hardware > in a mode that Windows doesn't (enabling AHCI in classcode 0101) seems > like asking for trouble. I agree we must be careful, for example we should put the controller back into its boot mode before suspending so that we can reasonably expect the BIOS to handle suspend/resume. And we certainly need an override option in one direction or the other. Nevertheless you don't make progress by limiting yourself to avoid breaking the most ancient system. We gave up having a man walking in front of cars with a red flag a long time ago. Alan - 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
