"I know bios", UEFI AHCI Driver (6)-ataatapipassthrusupported Local variables
Lightseed
5/7/2014
The previous 5 articles give a more detailed introduction to the installation of Efi_driver_binding_protocol, an example of this Protocol (instance) AHCI DRIVER. In fact this driver so far only to do one thing, that is to put this protocol installed to the corresponding imagehandle up. For this driver in the BDS how to run, the principle is to call supported () and then call Start (), and finally run stop () to unload driver. Recently listened to a lot of colleagues said to Thailand travel how cool, and later learned that really is a good choice. Just still owed a wife a honey moon, so this two weeks spent a lot of time to study the Raiders, wrote a part of the structure it. As the previous articles, in fact, are only a structure, the details need to do further research and discussion. It says so many things on the architecture. About Efi_driver_binding_protocol Let's continue to do a more in-depth discussion and study it thoroughly. For AHCI driver, start with its supported (). In the UEFI spec, there is a protocol called Efi_ata_pass_thru_protocol. It can actually not exist, the key is to see if the BIOS wants to support this feature. In fact, this protocol is encapsulated in different SATA controller modes such as IDE and AHCI. With this protocol, you can use this protocol to access SATA controllers in different modes in a fixed way and access the SATA devices that hang underneath them with a controller.
[Right click on the picture, open in a new window can be enlarged to see]