On Wed, 9 Jun 2021 at 09:30, Arnd Bergmann arnd@arndb.de wrote:
On Tue, Jun 8, 2021 at 6:49 PM Hans Verkuil hverkuil@xs4all.nl wrote:
On 08/06/2021 18:14, Arnd Bergmann wrote:
Right now it is inherent to the driver. It is probably possible to drop support for video overlay devices if CONFIG_FB=n, but it is not something I have time for. It's just a test driver (albeit a very useful test driver), so it is no big deal if it is disabled when CONFIG_FB=n.
Ok, thanks for the reply, makes sense.
I checked what other consequences there are if we disable CONFIG_FB and CONFIG_DRM_KMS_FB_HELPER=y in all the defconfigs now, as the patch from Kees did.
It appears that the only other arm32 framebuffers that remain are FB_EFI=y, FB_WM8505=y, FB_MX3=m and FB_SIMPLE=y.
FB_SH_MOBILE_LCDC on arm32 too.
As long as simplefb, efifb and xenfb are needed though, we probably want CONFIG_FB=y anyway and leaving VIVID=m with the dependency does not cause problems until those are all turned into drm drivers.
I will go ahead with this for the v7 defconfig.
Cheers,
Joel