Linux Framebuffer Layer development
 help / color / mirror / Atom feed
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: Tue, 18 Aug 2026 19:24:59 +0200	[thread overview]
Message-ID: <20260818172459.GA770905@ravnborg.org> (raw)
In-Reply-To: <CAEUXW=Ffs+WKsQrNc3zjwtfAO=FKTf_7jQFovD+yjmD_yJuY2Q@mail.gmail.com>

Hi Màxim.

On Tue, Aug 18, 2026 at 12:48:21AM +0200, Màxim Pedraza Padilla wrote:
> Hi Sam,
> 
> Thank you -- that's a useful pointer, and it settles the question of how
> a splash should be drawn without fbcon: a DRM client at
> drm_client_setup(), next to drm_log, not a drm_fb_helper hook.
> 
> Francesco's series is genuinely inspiring work, and it would be very
> useful to me if it could take a CLUT224 image -- unfortunately it can't.
> It only accepts an uncompressed 24-bit RGB888 BMP, whereas our logo is
> paletted, which is what keeps it small: 17 KiB for 800x480 rather than
> around a megabyte. So as it stands the format doesn't line up with what
> we carry.

Without looking at it in detail I would assume adding CLUT224 support
would be doable. Step 1 would be to add a format conversion in
drm_format_helper and use that. You may also find this useful for other
purposes.

	Sam

  reply	other threads:[~2026-08-18 17:25 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
2026-08-17 22:48                 ` Màxim Pedraza Padilla
2026-08-18 17:24                   ` Sam Ravnborg [this message]
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=20260818172459.GA770905@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