From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "John Hubbard" <jhubbard@nvidia.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Shashank Sharma" <shashanks@nvidia.com>,
"Zhi Wang" <zhiw@nvidia.com>, "David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
nova-gpu@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpu: nova-core: don't declare booter firmware for FSP chipsets
Date: Tue, 09 Jun 2026 15:06:40 +0900 [thread overview]
Message-ID: <DJ4AKA2J4158.1YSOLQE99O7IF@nvidia.com> (raw)
In-Reply-To: <20260607230539.144382-1-jhubbard@nvidia.com>
On Mon Jun 8, 2026 at 8:05 AM JST, John Hubbard wrote:
> The module firmware table lists booter_load and booter_unload for every
> chipset, but Hopper and Blackwell boot the GSP through FSP and never
> load the SEC2 booter. Those modinfo entries point at firmware files that
> are not shipped for FSP-based chipsets, so initramfs tooling looks for
> images that are never used.
>
> Declare the booter only for chipsets that boot via it, matching how the
> FMC and FWSEC bootloader images are already gated on chipset
> capabilities.
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
Pushed to `drm-rust-next`, thanks!
[acourbot: make comment on FMC/Booter choice a bit more precise.]
prev parent reply other threads:[~2026-06-09 6:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 23:05 [PATCH] gpu: nova-core: don't declare booter firmware for FSP chipsets John Hubbard
2026-06-08 22:09 ` Timur Tabi
2026-06-08 22:57 ` Danilo Krummrich
2026-06-09 0:00 ` Timur Tabi
2026-06-09 6:06 ` Alexandre Courbot [this message]
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=DJ4AKA2J4158.1YSOLQE99O7IF@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=shashanks@nvidia.com \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=zhiw@nvidia.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