audk/ShellPkg
Ruiyu Ni ff5a4bcff3 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>
2017-11-29 10:32:02 +08:00
..
Application ShellPkg: Fix the bug that handling Ctrl-C improperly 2017-11-29 09:07:26 +08:00
DynamicCommand ShellPkg/DynamicCommand: Fix bug that cannot start in boot 2017-11-29 10:32:02 +08:00
Include ShellPkg: Rename gShellCurDir to gShellCurMapping 2017-08-30 11:42:41 +08:00
Library ShellPkg/ShellLib: Fix dynamic command fails to start during boot 2017-11-29 10:31:54 +08:00
ShellPkg.dec ShellPkg: Update package version to 1.01 2017-05-03 10:44:55 +08:00
ShellPkg.dsc ShellPkg/DynamicCommand: Fix bug that cannot start in boot 2017-11-29 10:32:02 +08:00