From: Sam Ravnborg <sam@ravnborg.org>
To: "Màxim Pedraza Padilla" <maximpedraza@gmail.com>
Cc: "Maxime Ripard" <mripard@kernel.org>,
"Helge Deller" <deller@gmx.de>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, "Francesco Valla" <francesco@valla.it>
Subject: Re: [RFC PATCH 0/6] Boot logo supplied by the device tree
Date: Fri, 14 Aug 2026 17:53:25 +0200 [thread overview]
Message-ID: <20260814155325.GB516994@ravnborg.org> (raw)
In-Reply-To: <CAEUXW=H-o+fqBjH1UQG7=UTm5x1a9Cj++XJM7twvFU4vJC4UrQ@mail.gmail.com>
Hi Maxim.
> On doing it through KMS: you are right, and the follow-up series should be
> a DRM client alongside drm_log rather than a hook in drm_fb_helper. I will
> rework it that way before posting it.
Take a look at:
https://lkml.iu.edu/2605.1/03465.html
The work Francesco Valla did seems to overlap a lot with what you
suggest.
From the intro mail:
"
in a nutshell, the splash DRM client can draw a splashscreen using:
- the BMP image supplied by the EFI BGRT;
- a BMP image loaded as firmware (either built-in or loaded from the
filesystem);
- a colored background.
"
Sam
next prev parent reply other threads:[~2026-08-14 15:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 21:50 [RFC PATCH 0/6] Boot logo supplied by the device tree Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 1/6] dt-bindings: display: add a device tree supplied boot logo Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 2/6] video: logo: allow the boot logo to come from the device tree Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 3/6] fbdev: honour the device tree boot logo placement properties Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 4/6] dt-bindings: display: allow the boot logo in a reserved memory region Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 5/6] video: logo: allow the boot logo to come from " Max Pedraza
2026-07-31 21:50 ` [RFC PATCH 6/6] video: logo: add ppmtodtlogo host tool Max Pedraza
2026-08-01 8:08 ` [RFC PATCH 0/6] Boot logo supplied by the device tree Uwe Kleine-König
2026-08-01 20:44 ` Helge Deller
2026-08-01 22:01 ` Màxim Pedraza Padilla
2026-08-02 13:35 ` Uwe Kleine-König
2026-08-02 22:56 ` Màxim Pedraza Padilla
2026-08-10 9:02 ` Maxime Ripard
2026-08-12 0:31 ` Màxim Pedraza Padilla
2026-08-12 7:42 ` Maxime Ripard
2026-08-12 23:50 ` Màxim Pedraza Padilla
2026-08-13 8:02 ` Maxime Ripard
2026-08-13 23:50 ` Màxim Pedraza Padilla
2026-08-14 15:53 ` Sam Ravnborg [this message]
2026-08-17 22:48 ` Màxim Pedraza Padilla
2026-08-18 17:24 ` Sam Ravnborg
2026-08-18 19:39 ` Francesco Valla
2026-08-03 12:39 ` Ulrich Ölmann
2026-08-03 22:04 ` Màxim Pedraza Padilla
2026-08-04 5:25 ` Ulrich Ölmann
2026-08-04 15:59 ` Màxim Pedraza Padilla
2026-08-04 13:58 ` Geert Uytterhoeven
2026-08-04 22:37 ` Màxim Pedraza Padilla
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=20260814155325.GB516994@ravnborg.org \
--to=sam@ravnborg.org \
--cc=conor+dt@kernel.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=francesco@valla.it \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximpedraza@gmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
/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