This looks like a mashup of many commits from 3.3 which normally would
be a huge maintenance burden, but these changes are limited to cedarview
specific files (the code is duplicated out into each specific machine
generation) so it wont impact the other gma500 using drivers that do
work properly. The only changes not specific to cedarview are
diff --git a/drivers/staging/gma500/framebuffer.c
b/drivers/staging/gma500/framebuffer.c
index 3f39a37..07c1af8 100644
--- a/drivers/staging/gma500/framebuffer.c
+++ b/drivers/staging/gma500/framebuffer.c
@@ -244,7 +244,6 @@ static struct fb_ops psbfb_roll_ops = {
.fb_imageblit = cfb_imageblit,
.fb_pan_display = psbfb_pan,
.fb_mmap = psbfb_mmap,
- .fb_sync = psbfb_sync,
.fb_ioctl = psbfb_ioctl,
};
which is covered by this changelog note saying its safe to do on other
GPUs
- fix a bug where gtt roll mode called psbfb_sync, which tries to sync
the 2D engine. On other devices it is harmless as the 2D engine is
present but not in use when in gtt roll mode, on Cedartrail it causes
a hang
as well as converting 2 dev_err to dev_dbg to make them less verbose.
Given that GMA500 most likely wont receive updates in 3.2.x stable
releases because it moved out of staging a changed quite a bit the
burden seems minimal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944929
Title:
psb_gfx boot hang on Atom N2600 (GMA3600 Cedarview)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/944929/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
