From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Francesco Valla <francesco@valla.it>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
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 v2 1/3] drm: client: add splash client
Date: Tue, 6 Jan 2026 20:40:46 -0600 [thread overview]
Message-ID: <12c72476-a4e8-4b00-80ae-b8eed0b6f7a7@kernel.org> (raw)
In-Reply-To: <dedc1825-26ca-4976-b174-8d7a740e25e3@kernel.org>
>> Yes, that's the idea. I am still searching a EFI-enabled platform I can
>> perform some proper tests on, as I'm not really familiar with EFI.
>> This version was tested with OVMF on QEMU, but without a real userspace.
>
> Almost any modern x86 platform except for a chromebook uses EFI.
>
> I'll add them to my local dev tree and test too and see if I can get you
> some feedback if I run into any problems.
>
From my side when testing I hit this during kernel build:
ERROR: modpost: "bgrt_tab" [drivers/gpu/drm/clients/drm_client_lib.ko]
undefined!
ERROR: modpost: "bgrt_image_size"
[drivers/gpu/drm/clients/drm_client_lib.ko] undefined!
next prev parent reply other threads:[~2026-01-07 2:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 14:25 [PATCH RFC v2 0/3] Add splash DRM client Francesco Valla
2026-01-06 14:25 ` [PATCH RFC v2 1/3] drm: client: add splash client Francesco Valla
2026-01-06 14:47 ` Geert Uytterhoeven
2026-01-06 20:22 ` Francesco Valla
2026-01-06 18:58 ` Mario Limonciello (AMD) (kernel.org)
2026-01-06 20:32 ` Francesco Valla
2026-01-06 20:46 ` Mario Limonciello (AMD) (kernel.org)
2026-01-07 2:40 ` Mario Limonciello (AMD) (kernel.org) [this message]
2026-01-07 22:28 ` Francesco Valla
2026-01-22 13:36 ` Maxime Ripard
2026-01-23 20:59 ` Francesco Valla
2026-01-06 14:25 ` [PATCH RFC v2 2/3] MAINTAINERS: add entry for DRM " Francesco Valla
2026-01-06 14:25 ` [PATCH RFC v2 3/3] drm: docs: remove bootsplash from TODO Francesco Valla
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=12c72476-a4e8-4b00-80ae-b8eed0b6f7a7@kernel.org \
--to=superm1@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=mripard@kernel.org \
--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