forked from Minki/linux
3d6bd9065b
If simplefb was setup by our bootloader and enabled in the DT, we will have
a first framebuffer loaded in our system.
However, as soon as our DRM driver will load, it will reset the controller,
initialise it and, if the framebuffer emulation is enabled, register a
second framebuffer device.
This is obviously pretty bad, since the first framebuffer will be some kind
of a black hole, with memory still reserved that we can write to safely,
but not displayed anywhere.
Make sure we remove that framebuffer when we probe so we don't end up in
that situation.
Fixes:
|
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
sun4i_backend.c | ||
sun4i_backend.h | ||
sun4i_crtc.c | ||
sun4i_crtc.h | ||
sun4i_dotclock.c | ||
sun4i_dotclock.h | ||
sun4i_drv.c | ||
sun4i_drv.h | ||
sun4i_framebuffer.c | ||
sun4i_framebuffer.h | ||
sun4i_layer.c | ||
sun4i_layer.h | ||
sun4i_rgb.c | ||
sun4i_rgb.h | ||
sun4i_tcon.c | ||
sun4i_tcon.h | ||
sun4i_tv.c |