If you change the color depth via fbset or some other framebuffer aware
userland application struct fb_fix_screeninfo is not updated to this new
information. This patch fixes this issue. Also the function is changed to
just pass in struct drm_framebuffer so in the future we could use more
On Tue, Dec 21, 2010 at 08:29:03AM +0100, Michel D?nzer wrote:
On Die, 2010-12-21 at 11:41 +1000, Dave Airlie wrote:
From: Dave Airlie airl...@redhat.com
On my system with a radeon x2, the first GPU was not overlapping vesa
but the test decided it was.
Signed-off-by: Dave Airlie
On Tue, Dec 21, 2010 at 11:41:17AM +1000, Dave Airlie wrote:
From: Dave Airlie airl...@redhat.com
Situation as follow:
2 GPUs + vesafb + kms.
GPU 1 is primary, vesafb binds to it as fb0
radeon loads
GPU 0 loads as fb1
GPU 1 loads, vesafb gets kicked off which causes fb0 to unbind
