[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <27f14969-d71b-63db-7770-5269bf7b9ef1@redhat.com>
Date: Tue, 6 Dec 2022 15:14:22 +0100
From: Javier Martinez Canillas <javierm@...hat.com>
To: Thomas Zimmermann <tzimmermann@...e.de>, neil.armstrong@...aro.org,
Carlo Caione <ccaione@...libre.com>,
Daniel Vetter <daniel@...ll.ch>,
Jerome Brunet <jbrunet@...libre.com>,
David Airlie <airlied@...il.com>,
Kamlesh Gurudasani <kamlesh.gurudasani@...il.com>,
Mark Brown <broonie@...nel.org>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Kevin Hilman <khilman@...libre.com>
Cc: linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] drm/tiny: ili9486: remove conflicting framebuffers
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.
>>
>> 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 SPI display have been initialized by the firmware? If not, the
> call should be left out.
>
Agree.
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
Powered by blists - more mailing lists