Re: [PATCH RFC 0/3] Add splash DRM client

Maxime Ripard <[email protected]> Mon, 27 Oct 2025 17:28:58 +0100

Newsgroups	org.kernel.vger.linux-embedded,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel
Message-ID	<i7xxy33do4q4odvxxb77xv4ri5jgr6dup5kvfsjfs4h7mbmhrj@h3ke7h5whyvx>

On Mon, Oct 27, 2025 at 11:01:55AM -0500, Mario Limonciello wrote:
> On 10/27/25 7:35 AM, Thomas Zimmermann wrote:
> > > >    - a very simple progress bar, which can be driven through sysfs;
> > 
> > Once you have options to control these settings from user space, you
> > should do it in user space entirely. As Maxime suggested, please improve
> > plymouth for anything with animation.
> > 
> > > >    - a static image (optional).
> > 
> > Board vendors often provide an image, see /sys/firmware/acpi/bgrt/. This
> > is a candidate for display, or the penguin or a custom image. Please
> > make it configurable by Kconfig. Again, if you need policy and
> > heuristics for deciding what to display, you better do this in user
> > space.
> 
> I'd actually argue that the static image from BGRT should be the preferred
> priority.  This can make for a nice hand off to Plymouth.
> 
> The (UEFI) BIOS already will show this image as soon as the GOP driver is
> loaded.  Bootloaders like GRUB by default will avoid showing anything or
> will overwrite with the exact same image in the same location.  This can let
> the kernel do the same, and then the moment Plymouth takes over it could do
> the same.

And BGRT isn't typically found on embedded systems at all, so I'm not
sure it's a sensible default, let alone a priority. At most a possible
fallback.

Maxime

signature.asc (application/pgp-signature, 273 B)