diff options
| author | Ruiyu Ni <ruiyu.ni@intel.com> | 2017-11-28 19:43:16 +0800 |
|---|---|---|
| committer | Ruiyu Ni <ruiyu.ni@intel.com> | 2017-11-29 10:32:02 +0800 |
| commit | ff5a4bcff3e2afe4a94e62d457ccfc5361590067 (patch) | |
| tree | 413eca9a95863006bd5a60b5f704c8c1f889cefe /OvmfPkg/Sec | |
| parent | 68b07ebae5d7c4124ff7b2a8d35e2f8b6cda18b8 (diff) | |
| download | edk2-ff5a4bcff3e2afe4a94e62d457ccfc5361590067.tar.gz edk2-ff5a4bcff3e2afe4a94e62d457ccfc5361590067.tar.bz2 edk2-ff5a4bcff3e2afe4a94e62d457ccfc5361590067.zip | |
ShellPkg/DynamicCommand: Fix bug that cannot start in boot
When dynamic command drivers are built into FV and start during
boot, they fails. Because Shell protocol doesn't exist during boot.
The patch sets Shell protocol and also set PcdShellLibAutoInitialize
to FALSE to ensure that
1. Shell protocol check doesn't happen in driver's entry point.
2. Driver can get the Shell protocol in DynamicCommand.Handler().
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
Diffstat (limited to 'OvmfPkg/Sec')
0 files changed, 0 insertions, 0 deletions