diff options
| author | Yannick Heneault <yannick_heneault@matrox.com> | 2011-01-13 02:00:04 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2011-01-13 17:03:12 +0100 |
| commit | 554ec37aca8f5fbe4d70df462d7032aaa5d95ae9 (patch) | |
| tree | 5f572e6e9d43e8fbe097c4e0658719262ab14230 /drivers/rtc/rtc-omap.c | |
| parent | binfmt_elf: cleanups (diff) | |
| download | linux-554ec37aca8f5fbe4d70df462d7032aaa5d95ae9.tar.xz linux-554ec37aca8f5fbe4d70df462d7032aaa5d95ae9.zip | |
vgacon: check for efi machine
It seems there is a small problem of VGA palette corruption on EFI
machine. When the kernel initializes the architecture, it checks if the
machine is a EFI machine and assumes that a VGA console can exist.
When it initializes the console in vgacon_startup it checks if it can
really use the VGA console. I think this is where a check is missing.
Currently, the function can fail if a VESA boot mode is detected but not if
a EFI boot mode was used.
Thus vgacon_startup() doesn't fail and initialize the video card for a real
VGA mode. This function changes the first 16entries of the VGA palette.
When the efifb driver kicks in, the palette is not restored to default
ramp value, thus the 16 first entry remain in a modified state. The
following patch prevent this corruption.
Signed-off-by: Yannick Heneault <yheneaul@matrox.com>
Cc: Dave Airlie <airlied@linux.ie>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/rtc/rtc-omap.c')
0 files changed, 0 insertions, 0 deletions