Hello,
The edk2 produces several DXE drivers from the various packages.
I understand that these drivers can be loaded by using the shell "load"
command.
Are there any other methods to load DXE drivers from a shell
application? For example, one could have a DXE directory under \EFI
filesystem where a shell application could check for the DXE and installs it.
Better yet, it would great if the DXE Dispatcher could automatically
load drivers from this directory when needed.
A second option would be to embedded a DXE driver binary
into the shell application. The shell application could extract the DXE and
then install it.
A third possibility is to link the DXE code directly into the
application.
I haven't seen an example of this in the EDK2, so I assume this isn't
possible or suggested.
The reason I ask is that I am developing some simple shell utilities.
These utilities are usually passed around the company as single executables.
Having to carry around all the necessary DXEs for a shell application
is cumbersome and error prone.
Are there better methods for using DXEs than ones I've described?
Thanks,
Stephen
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
