diff options
author | Thomas Zimmermann <[email protected]> | 2019-11-26 11:15:29 +0100 |
---|---|---|
committer | Thomas Zimmermann <[email protected]> | 2019-11-27 08:11:11 +0100 |
commit | 1591fadf857cdbaf2baa55e421af99a61354713c (patch) | |
tree | 28c54d387c0919f05f0e86c315ada6ff9af15924 /lib/memory-notifier-error-inject.c | |
parent | d6d437d97d54c85a1a93967b2745e31dff03365a (diff) |
drm/mgag200: Add workaround for HW that does not support 'startadd'
There's at least one system that does not interpret the value of
the device's 'startadd' field correctly, which leads to incorrectly
displayed scanout buffers. Always placing the active scanout buffer
at offset 0 works around the problem.
Signed-off-by: Thomas Zimmermann <[email protected]>
Reported-by: John Donnelly <[email protected]>
Tested-by: John Donnelly <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Fixes: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin")
Cc: Gerd Hoffmann <[email protected]>
Cc: Dave Airlie <[email protected]>
Cc: Maarten Lankhorst <[email protected]>
Cc: Maxime Ripard <[email protected]>
Cc: David Airlie <[email protected]>
Cc: Sam Ravnborg <[email protected]>
Cc: "Y.C. Chen" <[email protected]>
Cc: Neil Armstrong <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: "José Roberto de Souza" <[email protected]>
Cc: Andrzej Pietrasiewicz <[email protected]>
Cc: [email protected]
Cc: <[email protected]> # v5.3+
Link: https://gitlab.freedesktop.org/drm/misc/issues/7
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions