diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2020-03-25 17:43:10 +0300 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2020-03-26 19:03:03 +0300 |
| commit | a65a97b48694d34248195eb89bf3687403261056 (patch) | |
| tree | 57dc66f08740e2eaf0c436be212b85c40d97341f /drivers/gpu/drm/vc4/vc4_hdmi.c | |
| parent | d021d751c14752a0266865700f6f212fab40a18c (diff) | |
| download | linux-a65a97b48694d34248195eb89bf3687403261056.tar.xz | |
drm/vboxvideo: Add missing remove_conflicting_pci_framebuffers call, v2
The vboxvideo driver is missing a call to remove conflicting framebuffers.
Surprisingly, when using legacy BIOS booting this does not really cause
any issues. But when using UEFI to boot the VM then plymouth will draw
on both the efifb /dev/fb0 and /dev/drm/card0 (which has registered
/dev/fb1 as fbdev emulation).
VirtualBox will actual display the output of both devices (I guess it is
showing whatever was drawn last), this causes weird artifacts because of
pitch issues in the efifb when the VM window is not sized at 1024x768
(the window will resize to its last size once the vboxvideo driver loads,
changing the pitch).
Adding the missing drm_fb_helper_remove_conflicting_pci_framebuffers()
call fixes this.
Changes in v2:
-Make the drm_fb_helper_remove_conflicting_pci_framebuffers() call one of
the first things we do in our probe() method
Cc: stable@vger.kernel.org
Fixes: 2695eae1f6d3 ("drm/vboxvideo: Switch to generic fbdev emulation")
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20200325144310.36779-1-hdegoede@redhat.com
Diffstat (limited to 'drivers/gpu/drm/vc4/vc4_hdmi.c')
0 files changed, 0 insertions, 0 deletions