Hi Reza, Take note that regarding SataControllerDxe, there still remains a problem that effects Qemu functionality.
On this query: Data32 = AhciReadReg (PciIo, R_AHCI_CAP); SataPrivateData->IdeInit.ChannelCount = (UINT8) ((Data32 & B_AHCI_CAP_NPS) + 1); qemu seems to always report 1 channel. This will end in only the first AHCI device being detected. As a temporal workaround, to allow all AHCI channels detected, you could change the second line to: SataPrivateData->IdeInit.ChannelCount = 6; but if you can, you should probably promote a fix at qemu's side for this. Cheers On Thu, Aug 7, 2014 at 3:07 PM, Reza Jelveh <[email protected]> wrote: > On 07/08/14 06:36, Zeng, Star wrote: > > I added SataControllerDxe in DuetPkg to support AHCI for Duet that has > chipset and platform specific initialization done before the Duet boot. > > It was thought to be hardly shared and used by real hardware platforms > as the platforms (at least all I touched) have their own SataControllerDxe > driver with some chipset policies or platform configurations. > > > Does anything speak against moving it to MdeModulePkg, so OVMF can use it > too? > > > ------------------------------------------------------------------------------ > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/edk2-devel >
------------------------------------------------------------------------------
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
