public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Helge Deller <deller@gmx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6] video/logo: allow custom boot logo and simplify logic
Date: Wed, 31 Dec 2025 07:46:40 +0100	[thread overview]
Message-ID: <0949ad6f-d703-47c9-8681-c64f17da07ac@kernel.org> (raw)
In-Reply-To: <12a2ee5ca1a085fe0bd0c1b2d6e08589445cbf66.camel@physik.fu-berlin.de>

On 31/12/2025 at 00:19, John Paul Adrian Glaubitz wrote:
> Hi Vincent,
> 
> On Tue, 2025-12-30 at 23:19 +0100, Vincent Mailhol wrote:
>> This series allows the user to replace the default kernel boot logo by
>> a custom one directly in the kernel configuration. This makes it
>> easier to customise the boot logo without the need to modify the
>> sources and allows such customisation to remain persistent after
>> applying the configuration to another version of the kernel.
> 
> Wouldn't it make more sense to make the boot logo to be configurable
> at runtime so that users don't have to rebuild their kernel at all
> to change their boot logo?

I thought about that. The problem is that the logo is loaded really
early in the boot process. To be able to modify the logo without
rebuilding the full kernel, the logo would basically need to become a
kernel module that would be stored in either an initrd or on the filesystem.

The above is not impossible, but would require delaying the logo.

If we go in that direction, I think that my series as it is right now
would be a prerequisite anyway. Personally, I am happy with the logo
just being configurable when compiling the kernel, so I do not intend to
put more effort into this afterward. However, that would have prepared
the ground if anyone wants to implement in the future what you just
suggested.


Yours sincerely,
Vincent Mailhol


  reply	other threads:[~2025-12-31  6:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 22:19 [PATCH 0/6] video/logo: allow custom boot logo and simplify logic Vincent Mailhol
2025-12-30 22:20 ` [PATCH 1/6] video/logo: remove orphan .pgm Makefile rule Vincent Mailhol
2026-01-02 16:34   ` David Heidelberg
2026-01-02 17:13     ` Vincent Mailhol
2026-01-02 17:18       ` David Heidelberg
2026-01-02 17:25         ` Vincent Mailhol
2026-01-02 19:59           ` Helge Deller
2026-01-02 20:20             ` Vincent Mailhol
2026-01-02 20:26             ` David Heidelberg
2025-12-30 22:20 ` [PATCH 2/6] video/logo: add a type parameter to the logo makefile function Vincent Mailhol
2025-12-30 22:20 ` [PATCH 3/6] video/logo: allow custom logo Vincent Mailhol
2025-12-30 22:20 ` [PATCH 4/6] newport_con: depend on LOGO_LINUX_CLUT224 instead of LOGO_SGI_CLUT224 Vincent Mailhol
2026-01-02 21:54   ` Vincent Mailhol
2025-12-30 22:20 ` [PATCH 5/6] sh: defconfig: remove CONFIG_LOGO_SUPERH_* Vincent Mailhol
2025-12-30 22:20 ` [PATCH 6/6] video/logo: move logo selection logic to Kconfig Vincent Mailhol
2026-01-01 13:17   ` Vincent Mailhol
2025-12-30 23:19 ` [PATCH 0/6] video/logo: allow custom boot logo and simplify logic John Paul Adrian Glaubitz
2025-12-31  6:46   ` Vincent Mailhol [this message]
2026-01-02 16:30 ` Markus Reichelt
2026-01-02 17:18   ` Vincent Mailhol
2026-01-02 19:55     ` Vincent Mailhol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0949ad6f-d703-47c9-8681-c64f17da07ac@kernel.org \
    --to=mailhol@kernel.org \
    --cc=dalias@libc.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox