On 06/12/2022 10:52, Thomas Zimmermann wrote:
Conflicting framebuffer on the SPI display ? How is that possible ?
Calling drm_aperture_remove_framebuffers() is only required if the
graphics card may have been pre-initialized by the system, such as a
VGA-compatible card on a PC.
Could the
For platforms using simplefb / efifb, call
drm_aperture_remove_framebuffers() to remove the conflicting
framebuffer.
Signed-off-by: Carlo Caione
---
drivers/gpu/drm/tiny/ili9486.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/tiny/ili9486.c
On 12/6/22 10:52, Thomas Zimmermann wrote:
> Hi
>
> Am 06.12.22 um 10:41 schrieb Neil Armstrong:
>> Hi Carlo,
>>
>> On 06/12/2022 09:34, Carlo Caione wrote:
>>> For platforms using simplefb / efifb, call
>>> drm_aperture_remove_framebuffers() to remove the conflicting
>>> framebuffer.
>>
>>
Hi
Am 06.12.22 um 10:41 schrieb Neil Armstrong:
Hi Carlo,
On 06/12/2022 09:34, Carlo Caione wrote:
For platforms using simplefb / efifb, call
drm_aperture_remove_framebuffers() to remove the conflicting
framebuffer.
Conflicting framebuffer on the SPI display ? How is that possible ?
Hi Carlo,
On 06/12/2022 09:34, Carlo Caione wrote:
For platforms using simplefb / efifb, call
drm_aperture_remove_framebuffers() to remove the conflicting
framebuffer.
Conflicting framebuffer on the SPI display ? How is that possible ?
The meson_drm should already do this, no ?
Neil
