diff options
author | Môshe van der Sterre <[email protected]> | 2016-02-01 22:07:03 +0000 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2016-02-03 11:41:19 +0100 |
commit | 66dbe99cfe30e113d2e571e68b9b6a1a8985a157 (patch) | |
tree | 9b6b51c7bc2ee49792ec8e1a6f7580f953f8ed44 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
parent | 9c09a342eb27902955ca939bd6ba29d875bd8b6b (diff) |
x86/efi/bgrt: Don't ignore the BGRT if the 'valid' bit is 0
Unintuitively, the BGRT graphic is apparently meant to be usable
if the valid bit in not set. The valid bit only conveys
uncertainty about the validity in relation to the screen state.
Windows 10 actually uses the BGRT image for its boot screen even
if not 'valid', for example when the user triggered the boot
menu. Because it is unclear if all firmwares will provide a
usable graphic in this case, we now look at the BMP magic number
as an additional check.
Reviewed-by: Josh Triplett <[email protected]>
Signed-off-by: Môshe van der Sterre <[email protected]>
Signed-off-by: Matt Fleming <[email protected]>
Cc: =?UTF-8?q?M=C3=B4she=20van=20der=20Sterre?= <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions