From: Maxime Ripard <mripard@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Francesco Valla <francesco@valla.it>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>,
Jocelyn Falempe <jfalempe@redhat.com>,
Javier Martinez Canillas <javierm@redhat.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: Re: [PATCH RFC 0/3] Add splash DRM client
Date: Mon, 27 Oct 2025 18:19:12 +0100 [thread overview]
Message-ID: <23clcxtgbzbsji2knwp47xdc5udj7lnhbvzsgqi3vklvmhdgjd@26ycx2ed77l4> (raw)
In-Reply-To: <93cbbaef-918f-4300-aa5b-11f098e217b2@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
On Mon, Oct 27, 2025 at 11:31:06AM -0500, Mario Limonciello wrote:
> On 10/27/25 11:28 AM, Maxime Ripard wrote:
> > 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
>
> There are certainly embedded machines using UEFI and that have a BGRT.
Yes, indeed, hence the "typically".
> How about "Sensible default the top of the priority list if it exists"
How about we don't tell contributors what their priorities must be?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2025-10-27 17:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 23:03 [PATCH RFC 0/3] Add splash DRM client Francesco Valla
2025-10-26 23:03 ` [PATCH RFC 1/3] drm: client: add splash client Francesco Valla
2025-10-26 23:03 ` [PATCH RFC 2/3] MAINTAINERS: add entry for DRM " Francesco Valla
2025-10-26 23:03 ` [PATCH RFC 3/3] drm: docs: remove bootsplash from TODO Francesco Valla
2025-10-27 10:09 ` [PATCH RFC 0/3] Add splash DRM client Maxime Ripard
2025-10-27 12:35 ` Thomas Zimmermann
2025-10-27 16:01 ` Mario Limonciello
2025-10-27 16:28 ` Maxime Ripard
2025-10-27 16:31 ` Mario Limonciello
2025-10-27 17:19 ` Maxime Ripard [this message]
2025-10-28 8:09 ` Francesco Valla
2025-10-28 13:39 ` Mario Limonciello
2025-10-29 8:36 ` Maxime Ripard
2025-10-28 8:03 ` Francesco Valla
2025-10-28 7:58 ` Francesco Valla
2025-10-29 8:34 ` Maxime Ripard
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=23clcxtgbzbsji2knwp47xdc5udj7lnhbvzsgqi3vklvmhdgjd@26ycx2ed77l4 \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=francesco@valla.it \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).