diff options
| author | Zack Rusin <zackr@vmware.com> | 2022-10-22 07:02:32 +0300 |
|---|---|---|
| committer | Zack Rusin <zackr@vmware.com> | 2022-10-25 19:42:27 +0300 |
| commit | df42523c12f8d58a41f547f471b46deffd18c203 (patch) | |
| tree | a8d756c9b8aa6f0b516f9243910bd6dc2252bc7f /crypto | |
| parent | 1c8d537bbcc9708d667d81ddc2caf43ec753cf05 (diff) | |
| download | linux-df42523c12f8d58a41f547f471b46deffd18c203.tar.xz | |
drm/vmwgfx: Port the framebuffer code to drm fb helpers
Instead of using vmwgfx specific framebuffer implementation use the drm
fb helpers. There's no change in functionality, the only difference
is a reduction in the amount of code inside the vmwgfx module.
drm fb helpers do not deal correctly with changes in crtc preferred mode
at runtime, but the old fb code wasn't dealing with it either.
Same situation applies to high-res fb consoles - the old code was
limited to 1176x885 because it was checking for legacy/deprecated
memory limites, the drm fb helpers are limited to the initial resolution
set on fb due to first problem (drm fb helpers being unable to handle
hotplug crtc preferred mode changes).
This also removes the kernel config for disabling fb support which hasn't
been used or supported in a very long time.
Signed-off-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Maaz Mombasawala <mombasawalam@vmware.com>
Reviewed-by: Martin Krastev <krastevm@vmware.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Link: https://patchwork.freedesktop.org/patch/msgid/20221022040236.616490-14-zack@kde.org
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions