From: Timur Tabi <ttabi@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
<nouveau@lists.freedesktop.org>, <rust-for-linux@vger.kernel.org>
Subject: [PATCH v5 03/11] gpu: nova-core: support header parsing on Turing/GA100
Date: Fri, 2 Jan 2026 22:59:26 -0600 [thread overview]
Message-ID: <20260103045934.64521-4-ttabi@nvidia.com> (raw)
In-Reply-To: <20260103045934.64521-1-ttabi@nvidia.com>
The Turing/GA100 version of Booter is slightly different from the
GA102+ version. The headers are the same, but different fields of
the headers are used to identify the IMEM section. In addition,
there is an NMEM section on Turing/GA100.
Signed-off-by: Timur Tabi <ttabi@nvidia.com>
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
---
drivers/gpu/nova-core/firmware/booter.rs | 28 ++++++++++++++++++++----
1 file changed, 24 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/nova-core/firmware/booter.rs b/drivers/gpu/nova-core/firmware/booter.rs
index 1b98bb47424c..86556cee8e67 100644
--- a/drivers/gpu/nova-core/firmware/booter.rs
+++ b/drivers/gpu/nova-core/firmware/booter.rs
@@ -356,14 +356,30 @@ pub(crate) fn new(
}
};
+ // There are two versions of Booter, one for Turing/GA100, and another for
+ // GA102+. The extraction of the IMEM sections differs between the two
+ // versions. Unfortunately, the file names are the same, and the headers
+ // don't indicate the versions. The only way to differentiate is by the Chipset.
+ let (imem_sec_dst_start, imem_ns_load_target) = if chipset <= Chipset::GA100 {
+ (
+ app0.offset,
+ Some(FalconLoadTarget {
+ src_start: 0,
+ dst_start: load_hdr.os_code_offset,
+ len: load_hdr.os_code_size,
+ }),
+ )
+ } else {
+ (0, None)
+ };
+
Ok(Self {
imem_sec_load_target: FalconLoadTarget {
src_start: app0.offset,
- dst_start: 0,
+ dst_start: imem_sec_dst_start,
len: app0.len,
},
- // Exists only in the booter image for Turing and GA100
- imem_ns_load_target: None,
+ imem_ns_load_target,
dmem_load_target: FalconLoadTarget {
src_start: load_hdr.os_data_offset,
dst_start: 0,
@@ -393,7 +409,11 @@ fn brom_params(&self) -> FalconBromParams {
}
fn boot_addr(&self) -> u32 {
- self.imem_sec_load_target.src_start
+ if let Some(ns_target) = &self.imem_ns_load_target {
+ ns_target.dst_start
+ } else {
+ self.imem_sec_load_target.src_start
+ }
}
}
--
2.51.0
next prev parent reply other threads:[~2026-01-03 4:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 4:59 [PATCH v5 00/11] gpu: nova-core: add Turing support Timur Tabi
2026-01-03 4:59 ` [PATCH v5 01/11] gpu: nova-core: rename Imem to ImemSecure Timur Tabi
2026-01-03 4:59 ` [PATCH v5 02/11] gpu: nova-core: add ImemNonSecure section infrastructure Timur Tabi
2026-01-03 4:59 ` Timur Tabi [this message]
2026-01-03 4:59 ` [PATCH v5 04/11] gpu: nova-core: add support for Turing/GA100 fwsignature Timur Tabi
2026-01-03 4:59 ` [PATCH v5 05/11] gpu: nova-core: add NV_PFALCON_FALCON_DMATRFCMD::with_falcon_mem() Timur Tabi
2026-01-03 4:59 ` [PATCH v5 06/11] gpu: nova-core: move some functions into the HAL Timur Tabi
2026-01-03 4:59 ` [PATCH v5 07/11] gpu: nova-core: Add basic Turing HAL Timur Tabi
2026-01-03 4:59 ` [PATCH v5 08/11] gpu: nova-core: add Falcon HAL method supports_dma() Timur Tabi
2026-01-09 0:25 ` John Hubbard
2026-01-03 4:59 ` [PATCH v5 09/11] gpu: nova-core: add FalconUCodeDescV2 support Timur Tabi
2026-01-09 2:53 ` John Hubbard
2026-01-09 18:11 ` Timur Tabi
2026-01-09 18:59 ` John Hubbard
2026-01-09 19:13 ` John Hubbard
2026-01-13 1:08 ` John Hubbard
2026-01-13 0:00 ` Joel Fernandes
2026-01-14 0:56 ` Timur Tabi
2026-01-14 0:59 ` Joel Fernandes
2026-01-03 4:59 ` [PATCH v5 10/11] gpu: nova-core: align LibosMemoryRegionInitArgument size to page size Timur Tabi
2026-01-09 3:15 ` John Hubbard
2026-01-03 4:59 ` [PATCH v5 11/11] gpu: nova-core: add PIO support for loading firmware images Timur Tabi
2026-01-03 12:53 ` kernel test robot
2026-01-05 23:44 ` [PATCH v5 00/11] gpu: nova-core: add Turing support Timur Tabi
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=20260103045934.64521-4-ttabi@nvidia.com \
--to=ttabi@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=nouveau@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.org \
/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