]> git.baikalelectronics.ru Git - kernel.git/commit
staging: gma500: get control from firmware framebuffer if conflicts
authorMichael Chang <mchang@novell.com>
Mon, 30 May 2011 06:28:25 +0000 (14:28 +0800)
committerGreg Kroah-Hartman <gregkh@suse.de>
Tue, 7 Jun 2011 19:28:42 +0000 (12:28 -0700)
commit2e01a8318b6128d16a1fed650eb1ca54a540ee6a
tree590f9ff7476d8590a27254ce0c023b2791b0b35e
parente7c94c97f31a55d8035a4bccbb8bf0e5e1567c2f
staging: gma500: get control from firmware framebuffer if conflicts

Many Linux distributions would enable vesafb in order to display
early stage boot splash. In this case, we will get garbled X
Window screen if running X fbdev on psbfb.

This is because fb0 is occupied by vesafb while psbfb is on fb1.
They tried to drive the same pieces of hardware at the same
time. With unmodified X start-up, it would try to use default
fb0 framebuffer device and unfortunately it is now broken
becaues fb1 supersedes it.

We should let psbfb takeover framebuffer control from vesafb
to get around this problem.

See also commit : bce33abbb8ed1b8660d436a4e98bf95998146928

Signed-off-by: Michael Chang <mchang@novell.com>
Cc: Alan Cox <alan@linux.intel.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/staging/gma500/psb_fb.c