diff options
| author | Matthew Garrett <[email protected]> | 2012-07-27 17:20:49 -0400 |
|---|---|---|
| committer | Matt Fleming <[email protected]> | 2012-09-17 13:29:24 +0100 |
| commit | e9b10953edbccd3744e039ffc060ab2692f17856 (patch) | |
| tree | 624e3106d263cef39059348d7f90edf75f83feef /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | f462ed939de67c20528bc08f11d2fc4f2d59c0d5 (diff) | |
x86, EFI: Calculate the EFI framebuffer size instead of trusting the firmware
Seth Forshee reported that his system was reporting that the EFI framebuffer
stretched from 0x90010000-0xb0010000 despite the GPU's BAR only covering
0x90000000-0x9ffffff. It's safer to calculate this value from the pixel
stride and screen height (values we already depend on) rather than face
potential problems with resource allocation later on.
Signed-off-by: Matthew Garrett <[email protected]>
Tested-by: Seth Forshee <[email protected]>
Signed-off-by: Matt Fleming <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions