> return to real mode after Linux). This proprietary code makes use of the BIOS > disk calls via int13. In short we need to the BIOS Int13 after Linux. Thats tricky. Linux does preserve the BIOS page. > I been looking though your archives and reading the AHCI spec. It seems clear > that the hardware has at least some state contained within it; I'm wondering if > there is any hope of putting the chip back to a known state that the BIOS will > be able to handle. You want the chip docs for the specific AHCI controller you need to work with. For the Intel ones at least yo've got a chance to reconfigure them. However you will need to know what the BIOS expects. You may well also find that if you use a BIOS that supports AHCI (and can set the controller to AHCI) you can use INT13 to talk to the controller in AHCI mode. I don't think its a good idea, and I would be tempted to try and remove that set of calls and fire them via an application in Linux before calling kexec, but in theory yes you can probably put the device back into legacy mode. 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
