drivers/video/logo/Kconfig | 2 -- 1 file changed, 2 deletions(-)
Nowadays, nearly all systems have a color depth of eight or more and
are thus able to display the clut224 logo. This means that the
monochrome and vga16 logos will never be displayed on an average
machine and are thus just a waste of bytes.
Set CONFIG_LOGO_LINUX_MONO and CONFIG_LOGO_LINUX_VGA16 configuration
symbols to no by default.
Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
To be applied on top of my previous "video/logo: allow custom boot
logo and simplify logic" series:
Link: https://lore.kernel.org/all/20260108-custom-logo-v3-0-5a7aada7a6d4@kernel.org/
---
drivers/video/logo/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/video/logo/Kconfig b/drivers/video/logo/Kconfig
index 34ee207e5e77..cda15b95891e 100644
--- a/drivers/video/logo/Kconfig
+++ b/drivers/video/logo/Kconfig
@@ -20,7 +20,6 @@ config FB_LOGO_EXTRA
config LOGO_LINUX_MONO
bool "Standard black and white Linux logo"
- default y
config LOGO_LINUX_MONO_FILE
string "Monochrome logo .pbm file"
@@ -38,7 +37,6 @@ config LOGO_LINUX_MONO_FILE
config LOGO_LINUX_VGA16
bool "Standard 16-color Linux logo"
- default y
config LOGO_LINUX_VGA16_FILE
string "16-color logo .ppm file"
---
base-commit: f10c325a345fef0a688a2bcdfab1540d1c924148
change-id: 20260110-mono_and_vga16_logos_default_to_no-fea83b350250
prerequisite-change-id: 20251227-custom-logo-932df316a02c:v3
prerequisite-patch-id: 5053eddfae57689a621f3224acc18742a25c2887
prerequisite-patch-id: 2fd02272fb8f94575c67124366f58811dcceb6ad
prerequisite-patch-id: 81d5632ac8717a56b335bb356e8fe5d9e8b1639f
prerequisite-patch-id: 268d8fb7ce93d0cb137c32b6f149fda376da37e8
prerequisite-patch-id: f6229ba399af73d57a647050a8f0f6871c4a96ef
prerequisite-patch-id: 6a6d392a9acf6eb2fe2827e3beebbc4b341f50a5
prerequisite-patch-id: 359180711835dc73be129380a5664210e19d50f1
Best regards,
--
Vincent Mailhol <mailhol@kernel.org>
On 1/10/26 13:23, Vincent Mailhol wrote: > Nowadays, nearly all systems have a color depth of eight or more and > are thus able to display the clut224 logo. This means that the > monochrome and vga16 logos will never be displayed on an average > machine and are thus just a waste of bytes. > > Set CONFIG_LOGO_LINUX_MONO and CONFIG_LOGO_LINUX_VGA16 configuration > symbols to no by default. I agree, that on basically every system today there is no need for the monochrome or VGA16 logo. But I'm not sure about the historic/exotic platforms, e.g. m68, sparc and so on. So, maybe instead of dropping the default "y", we should e.g. do: + default y if SUPERH + default y if XYZ (some other architecture/platform) ??? + default n (for all others) The question is: Which arches may have needed the VGA16 or monochrome logo? Helge > Signed-off-by: Vincent Mailhol <mailhol@kernel.org> > --- > To be applied on top of my previous "video/logo: allow custom boot > logo and simplify logic" series: > > Link: https://lore.kernel.org/all/20260108-custom-logo-v3-0-5a7aada7a6d4@kernel.org/ > --- > drivers/video/logo/Kconfig | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/drivers/video/logo/Kconfig b/drivers/video/logo/Kconfig > index 34ee207e5e77..cda15b95891e 100644 > --- a/drivers/video/logo/Kconfig > +++ b/drivers/video/logo/Kconfig > @@ -20,7 +20,6 @@ config FB_LOGO_EXTRA > > config LOGO_LINUX_MONO > bool "Standard black and white Linux logo" > - default y > > config LOGO_LINUX_MONO_FILE > string "Monochrome logo .pbm file" > @@ -38,7 +37,6 @@ config LOGO_LINUX_MONO_FILE > > config LOGO_LINUX_VGA16 > bool "Standard 16-color Linux logo" > - default y > > config LOGO_LINUX_VGA16_FILE > string "16-color logo .ppm file" > > --- > base-commit: f10c325a345fef0a688a2bcdfab1540d1c924148 > change-id: 20260110-mono_and_vga16_logos_default_to_no-fea83b350250 > prerequisite-change-id: 20251227-custom-logo-932df316a02c:v3 > prerequisite-patch-id: 5053eddfae57689a621f3224acc18742a25c2887 > prerequisite-patch-id: 2fd02272fb8f94575c67124366f58811dcceb6ad > prerequisite-patch-id: 81d5632ac8717a56b335bb356e8fe5d9e8b1639f > prerequisite-patch-id: 268d8fb7ce93d0cb137c32b6f149fda376da37e8 > prerequisite-patch-id: f6229ba399af73d57a647050a8f0f6871c4a96ef > prerequisite-patch-id: 6a6d392a9acf6eb2fe2827e3beebbc4b341f50a5 > prerequisite-patch-id: 359180711835dc73be129380a5664210e19d50f1 > > Best regards,
On 11/01/2026 at 20:12, Helge Deller wrote: > On 1/10/26 13:23, Vincent Mailhol wrote: >> Nowadays, nearly all systems have a color depth of eight or more and >> are thus able to display the clut224 logo. This means that the >> monochrome and vga16 logos will never be displayed on an average >> machine and are thus just a waste of bytes. >> >> Set CONFIG_LOGO_LINUX_MONO and CONFIG_LOGO_LINUX_VGA16 configuration >> symbols to no by default. > > I agree, that on basically every system today there is no need for the > monochrome or VGA16 logo. > But I'm not sure about the historic/exotic platforms, e.g. m68, sparc > and so on. > > So, maybe instead of dropping the default "y", we should e.g. do: > + default y if SUPERH SUPERH also has a clut224 logo, so I assume we can also default to no for it. > + default y if XYZ (some other architecture/platform) ??? > + default n (for all others) > > The question is: Which arches may have needed the VGA16 or monochrome logo? My wild guess would be none. Furthermore, no one "needs" a logo. It is just a fun thing to add. This is why the LOGO sub menu is turned off by default and that none of the defconfig would automatically select a LOGO. And so, because a user interaction is needed anyway, the few who still want a monochrome or vga16 logo can turn the option back on just after selecting the LOGO sub-menu. I guess the same could be said in reverse: we could keep all the logo on by default as it is now and the users who only need the clut224 can turn off the monochrome and vga16. But let's go for the majority ;) Well, if someone can come with the list you are looking for, I will happily add it to the patch. We can wait for a couple weeks if you want, no rush here! Or your can already stage it in fbdev-next and I will send you a v2 as needed. Maybe we will get more comments if this reaches linux-next? Yours sincerely, Vincent Mailhol
© 2016 - 2026 Red Hat, Inc.