From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Russ Weight" <russ.weight@linux.dev>,
"Gary Guo" <gary@garyguo.net>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"John Hubbard" <jhubbard@nvidia.com>, <zhiw@nvidia.com>,
<rust-for-linux@vger.kernel.org>, <driver-core@lists.linux.dev>,
<nova-gpu@lists.linux.dev>
Subject: Re: [PATCH v7 0/8] Transition Nova Core to TLV firmware images
Date: Mon, 03 Aug 2026 22:51:54 +0900 [thread overview]
Message-ID: <DKFCWGG1VRLY.3BGUVD5H17KSZ@nvidia.com> (raw)
In-Reply-To: <20260731201017.2580713-1-ttabi@nvidia.com>
On Sat Aug 1, 2026 at 5:10 AM JST, Timur Tabi wrote:
> This patch set transitions nova-core to use the new "TLV" firmware image
> files, instead of the ones that Nouveau uses.
>
> A prerequisite patch "rust: error: add remaining error codes" is required
> to compile. [1]
>
> The current r570.144 images are a mix of binary headers and ELF files that
> are cumbersome to parse in Rust. There's a significant amount of code
> that just reads in a struct, extracts some offset, and uses it to find
> another struct, only to have nova-core use just a few fields.
>
> The new format uses a sequence of tag/length/value fields that can be
> iterated over. The script that generates the TLV files,
> extract-firmware-nova.py, does the extra work to find the specific metadata
> needed by Nova and packages each one separately.
>
> The TLV versions of r570.144 can be found here:
>
> https://github.com/ttabi/linux-firmware-nova
>
> along with instructions on how to install them. We are not planning on
> submitting these images to linux-firmware. Rather, if this patchset
> is accepted upstream, I expect the small handful of people who are
> actually working on Nova to grab and install these images, which needs
> to be done only once.
>
> There are still opportunities for improvement. For example, I would like
> to get rid of more GPU-specific code, especially the GA100 quirks.
>
> Note that there are plans to relocate these images into a different
> /lib/firmware subdirectory, to further isolate them from the images that
> Nouveau uses.
>
> [1] https://lore.kernel.org/rust-for-linux/20260629183022.2709524-1-ttabi@nvidia.com/
Gave the series a run on tu106, ga107 and gb203, all successfully. Each
patch also builds nicely without warnings or formatting issues.
Since this also touches core Rust parts, it is preferable that Danilo
merges it, so for the series:
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Tested-by: Alexandre Courbot <acourbot@nvidia.com>
(note that [1] is also needed)
[1] https://lore.kernel.org/all/20260629183022.2709524-1-ttabi@nvidia.com/
prev parent reply other threads:[~2026-08-03 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 20:10 [PATCH v7 0/8] Transition Nova Core to TLV firmware images Timur Tabi
2026-07-31 20:10 ` [PATCH v7 1/8] rust: alloc: add Vec::zeroed method Timur Tabi
2026-08-03 21:22 ` Danilo Krummrich
2026-07-31 20:10 ` [PATCH v7 2/8] rust: firmware: add request_into_buf() Timur Tabi
2026-07-31 20:10 ` [PATCH v7 3/8] gpu: nova-core: add TLV parser for firmware files Timur Tabi
2026-08-03 21:36 ` Danilo Krummrich
2026-08-03 21:38 ` Danilo Krummrich
2026-08-03 22:05 ` Timur Tabi
2026-08-03 22:21 ` Danilo Krummrich
2026-07-31 20:10 ` [PATCH v7 4/8] gpu: nova-core: transition booter to TLV images Timur Tabi
2026-07-31 20:10 ` [PATCH v7 5/8] gpu: nova-core: transition gsp " Timur Tabi
2026-07-31 20:10 ` [PATCH v7 6/8] gpu: nova-core: transition gen_bootloader " Timur Tabi
2026-07-31 20:10 ` [PATCH v7 7/8] gpu: nova-core: transition fsp " Timur Tabi
2026-07-31 20:10 ` [PATCH v7 8/8] gpu: nova-core: update firmware module info for " Timur Tabi
2026-08-03 13:51 ` 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=DKFCWGG1VRLY.3BGUVD5H17KSZ@nvidia.com \
--to=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=mcgrof@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--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