Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=linux-7.0.y 2026-02-14T10:09:46+00:00 2026-02-14T10:09:46+00:00 Vincent Mailhol mailhol@kernel.org 2026-01-08T19:04:55+00:00 urn:sha1:ac6d088b3b20f9efb883e8302288276db3bdc2b8 Now that the path to the logo file can be directly entered in Kbuild, there is no more need to handle all the logo file selection in the Makefile and the C files. The only exception is the logo_spe_clut224 which is only used by the Cell processor (found for example in the Playstation 3) [1]. This extra logo uses its own different image which shows up on a separate line just below the normal logo. Because the extra logo uses a different image, it can not be factorized under the custom logo logic. Move all the logo file selection logic to Kbuild (except from the logo_spe_clut224.ppm), this done, clean-up the C code to only leave one entry for each logo type (monochrome, 16-colors and 224-colors). [1] Cell SPE logos Link: https://lore.kernel.org/all/20070710122702.765654000@pademelon.sonytel.be/ Signed-off-by: Vincent Mailhol <mailhol@kernel.org> Signed-off-by: Helge Deller <deller@gmx.de> 2026-02-14T10:09:46+00:00 Vincent Mailhol mailhol@kernel.org 2026-01-08T19:04:54+00:00 urn:sha1:3092718e1280fcbdfc4f4b4a3258be8992a0c244 The logo_mac_clut224 depends on the runtime value MACH_IS_MAC being true to be displayed. This makes that logo a one-of-a-kind, as it is the only one whose selection can not be decided at compile time. This dynamic logo selection logic conflicts with our upcoming plans to simplify the logo selection code. Considering that the logo_mac_clut224 is only used by the Macintosh 68k, a machine whose sales ended some thirty years ago and which thus represents a very small user base, it is preferable to resolve the conflict in favour of code simplicity. Remove the logo_mac_clut224 so that the logo selection can be statically determined at compile time. The users who wish to continue using that logo can still download it from [1] and add: CONFIG_LOGO_LINUX_CLUT224=y CONFIG_LOGO_LINUX_CLUT224_FILE="/path/to/logo_mac_clut224.ppm" to their configuration file to restore it. [1] logo_mac_clut224.ppm file Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/drivers/video/logo/logo_mac_clut224.ppm?h=v6.18 Signed-off-by: Vincent Mailhol <mailhol@kernel.org> Signed-off-by: Helge Deller <deller@gmx.de> 2026-02-14T10:09:46+00:00 Vincent Mailhol mailhol@kernel.org 2026-01-08T19:04:51+00:00 urn:sha1:dfa6ce636cb8faeaef02b09c973400a410004edf Some people like to replace the default Tux boot logo by an image of their own. There exist a few tutorials here [1] and there [2]. But this requires modifying the source tree which is a bit cumbersome. Add a string entry in Kbuild for each of the logo categories (monochrome, 16-colors, 224-colors). The string entry takes a path to a .pbm or .ppm image allowing the user to more easily provide a custom logo without having to modify the sources. Add an help entry with a short hint on how to convert images to the portable pixmap file format. Update the Makefile accordingly. When converted to .c file, the logo will have one of these fixed file name: - logo_linux_mono.c - logo_linux_vga16.c - logo_linux_clut224.c: depending on the image type and this regardless of the name of the .pgm/.ppm source filename. This will allow for further simplifications in an upcoming change. [1] ArmadeuS Project wiki -- Linux Boot Logo Link: https://www.armadeus.org/wiki/index.php?title=Linux_Boot_Logo [2] Timesys -- How To Use a Custom Boot Logo / Splash Screen Link: https://linuxlink.timesys.com/docs/wiki/engineering/HOWTO_Use_a_custom_boot_logo Signed-off-by: Vincent Mailhol <mailhol@kernel.org> Signed-off-by: Helge Deller <deller@gmx.de> 2026-02-14T10:09:46+00:00 Vincent Mailhol mailhol@kernel.org 2026-01-08T19:04:50+00:00 urn:sha1:a7aa2b512b141afe638b715f7b84c1588cdc9845 When translating a portable pixmap file into a .c file, the pnmtologo tool expects to receive the image type (either mono, vga16 or clut224) as an argument under the -t option. Currently, this information is stored in the file name. Because we will allow for custom logo in an upcoming change, it is preferable to decouple the image name from its type. Add a new $2 parameter to the Makefile logo function which contains the image type. Update all the individual targets to provide this new argument. Signed-off-by: Vincent Mailhol <mailhol@kernel.org> Signed-off-by: Helge Deller <deller@gmx.de> 2026-02-14T10:09:46+00:00 Vincent Mailhol mailhol@kernel.org 2026-01-08T19:04:49+00:00 urn:sha1:672b35216282199fa2906fb32697a25a686a1adc The kernel has no actual grey-scale logos. And looking at the git history, it seems that there never was one (or maybe there was in the pre-git history? I did not check that far…) Remove the Makefile rule for the .pgm grey scale images. Signed-off-by: Vincent Mailhol <mailhol@kernel.org> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Helge Deller <deller@gmx.de> 2020-02-03T16:53:07+00:00 Masahiro Yamada masahiroy@kernel.org 2020-02-01T16:49:24+00:00 urn:sha1:5f2fb52fac15a8a8e10ce020dd532504a8abfc4e In old days, the "host-progs" syntax was used for specifying host programs. It was renamed to the current "hostprogs-y" in 2004. It is typically useful in scripts/Makefile because it allows Kbuild to selectively compile host programs based on the kernel configuration. This commit renames like follows: always -> always-y hostprogs-y -> hostprogs So, scripts/Makefile will look like this: always-$(CONFIG_BUILD_BIN2C) += ... always-$(CONFIG_KALLSYMS) += ... ... hostprogs := $(always-y) $(always-m) I think this makes more sense because a host program is always a host program, irrespective of the kernel configuration. We want to specify which ones to compile by CONFIG options, so always-y will be handier. The "always", "hostprogs-y", "hostprogs-m" will be kept for backward compatibility for a while. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> 2019-11-11T11:07:03+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2019-08-21T04:12:37+00:00 urn:sha1:78a20a012ecea857e438b1f9e8091acb290bd0f5 This tool is only used by drivers/video/logo/Makefile. No reason to keep it in scripts/. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-11-11T11:07:03+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2019-08-21T04:12:36+00:00 urn:sha1:e3c639b899335684a2c675632524ae561cd326d2 Shorten the code. It still works in the same way. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-10-05T06:29:49+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2019-08-21T04:12:35+00:00 urn:sha1:01bb25156d856e3efb887a273c03f8ba66f8fb0f Currently, all the logo C files are generated irrespective of the CONFIG options. Adding them to extra-y is wrong. What we need to do here is to add them to 'targets' so that if_changed works properly. Files listed in 'targets' are cleaned, so clean-files is unneeded. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-10-05T06:29:49+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2019-08-21T04:12:34+00:00 urn:sha1:a9bbe79fd5cb2411d69ab8a2e94bb701ca45e133 The pattern *.o is cleaned up globally by the top Makefile. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>