From: Matthew Garrett <mjg@redhat.com>
Date: Fri, 27 Jul 2012 21:20:49 +0000 (-0400)
Subject: x86, EFI: Calculate the EFI framebuffer size instead of trusting the firmware
X-Git-Tag: omap-for-v3.7-rc1/fixes-cpufreq-signed~87^2~3^2
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e9b10953edbccd3744e039ffc060ab2692f17856;p=pandora-kernel.git

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 <mjg@redhat.com>
Tested-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
---

Reading git-diff-tree failed