diff options
author | Rob Clark <robdclark@gmail.com> | 2013-11-16 13:39:36 -0500 |
---|---|---|
committer | Rob Clark <robdclark@gmail.com> | 2013-11-16 13:39:36 -0500 |
commit | 75bf4933c4705145efe8bd8d0e7cf31a64ebe2d9 (patch) | |
tree | 301e116dd99643f8bb50b2bfa9de04b7b37953dd | |
parent | ca53ae8fbf831ab60e46123e85099ec737b98918 (diff) |
fbdev: fix 0x0 visual issue
The framebuffer dimensions are not retrieved before they are first used,
when using msm fbdev driver, resulting in X clients thinking the display
is 0x0. Which results in window placement issues, etc.
Signed-off-by: Rob Clark <robdclark@gmail.com>
-rw-r--r-- | src/fbmode_display.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/fbmode_display.c b/src/fbmode_display.c index 8752fcd..357c16e 100644 --- a/src/fbmode_display.c +++ b/src/fbmode_display.c @@ -81,6 +81,8 @@ typedef struct { #define MSM_CURSOR_WIDTH 64 #define MSM_CURSOR_HEIGHT 64 +static void MSMGetDefaultMode(fbmode_ptr fbmode); + static fbmode_ptr fbmode_from_scrn(ScrnInfoPtr scrn) @@ -433,6 +435,7 @@ static DisplayModePtr MSMOutputGetModes(xf86OutputPtr output) { fbmode_ptr fbmode = output->driver_private; + MSMGetDefaultMode(fbmode); return xf86DuplicateMode(&fbmode->default_mode); } |