diff options
| author | lijuang <lijuang@codeaurora.org> | 2016-08-16 16:13:19 +0800 |
|---|---|---|
| committer | lijuang <lijuang@codeaurora.org> | 2016-08-17 10:38:38 +0800 |
| commit | 4734bc8cfbf76a6e0f6f66009d003b4d0711c62a (patch) | |
| tree | 0c391d5afa8ad5861e921dab887d35607093c334 /QcomModulePkg/Library/BootLib/MenuKeysDetection.c | |
| parent | 4d237a5d2f1d7c4e2cd86fb249e1c76bf1739ed3 (diff) | |
QcomModulePkg: Library: Remove ASSERTS from draw UI functions
Remove the ASSERTS from UI related functions. It will cause the device
couldn't boot up if the display component is not enabled in core UEFI.
It should be gracefully exit UI related functions.
Modified:
1. Print error log instead of ASSERT device
2. Don't draw UI to the screen if it's failed to get graphics info
3. Don't create event to detect key's status
CRs-Fixed: 1055175
Change-Id: Icf004140d1a1faea205b142b9b922ac847af306d
Diffstat (limited to 'QcomModulePkg/Library/BootLib/MenuKeysDetection.c')
| -rw-r--r-- | QcomModulePkg/Library/BootLib/MenuKeysDetection.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/QcomModulePkg/Library/BootLib/MenuKeysDetection.c b/QcomModulePkg/Library/BootLib/MenuKeysDetection.c index f7bbe5a580..f994734967 100644 --- a/QcomModulePkg/Library/BootLib/MenuKeysDetection.c +++ b/QcomModulePkg/Library/BootLib/MenuKeysDetection.c @@ -418,13 +418,13 @@ EFI_STATUS EFIAPI MenuKeysDetectionInit(IN VOID *mMenuInfo) MenuInfo, &CallbackKeyDetection ); - DEBUG((EFI_D_INFO, "Create keys detection event: %r\n", Status)); + DEBUG((EFI_D_VERBOSE, "Create keys detection event: %r\n", Status)); if (!EFI_ERROR (Status)) { Status = gBS->SetTimer(CallbackKeyDetection, TimerPeriodic, 500000); - DEBUG((EFI_D_INFO, "Set keys detection Timer: %r\n", Status)); + DEBUG((EFI_D_VERBOSE, "Set keys detection Timer: %r\n", Status)); } } return Status; |