rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Lyude Paul" <lyude@redhat.com>, <nouveau@lists.freedesktop.org>,
	<rust-for-linux@vger.kernel.org>
Cc: "Nouveau" <nouveau-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v3 04/12] gpu: nova-core: add support for Turing/GA100 fwsignature
Date: Wed, 17 Dec 2025 15:27:10 +0900	[thread overview]
Message-ID: <DF0A16OM1I4A.3HGXMFWBP34IF@nvidia.com> (raw)
In-Reply-To: <20251208231801.1786803-5-ttabi@nvidia.com>

On Tue Dec 9, 2025 at 8:17 AM JST, Timur Tabi wrote:
> Turing and GA100 share the same GSP-RM firmware binary, and the
> signature ELF section is labeled ".fwsignature_tu10x".
>
> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
> ---
>  drivers/gpu/nova-core/firmware/gsp.rs | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/nova-core/firmware/gsp.rs b/drivers/gpu/nova-core/firmware/gsp.rs
> index 0549805282ab..aa5a6433c377 100644
> --- a/drivers/gpu/nova-core/firmware/gsp.rs
> +++ b/drivers/gpu/nova-core/firmware/gsp.rs
> @@ -163,9 +163,14 @@ pub(crate) fn new<'a, 'b>(
>          let fw_section = elf::elf64_section(fw.data(), ".fwimage").ok_or(EINVAL)?;
>  
>          let sigs_section = match chipset.arch() {
> -            Architecture::Ampere => ".fwsignature_ga10x",
> +            Architecture::Turing | Architecture::Ampere =>
> +                if chipset > Chipset::GA100 {
> +                    ".fwsignature_ga10x"
> +                } else {
> +                    // GA100 uses the same firmware as Turing
> +                    ".fwsignature_tu10x"
> +                },

Please use the pattern discussed in [1] here as it better expresses the
exception for GA100.

[1] https://lore.kernel.org/all/0f11194b-edb4-4206-9a6c-b7ada3cba3e8@nvidia.com/

  reply	other threads:[~2025-12-17  6:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 23:17 [PATCH v3 00/12] gpu: nova-core: add Turing support Timur Tabi
2025-12-08 23:17 ` [PATCH v3 01/12] gpu: nova-core: rename Imem to ImemSecure Timur Tabi
2025-12-08 23:17 ` [PATCH v3 02/12] gpu: nova-core: add ImemNonSecure section infrastructure Timur Tabi
2025-12-08 23:17 ` [PATCH v3 03/12] gpu: nova-core: support header parsing on Turing/GA100 Timur Tabi
2025-12-17  6:23   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 04/12] gpu: nova-core: add support for Turing/GA100 fwsignature Timur Tabi
2025-12-17  6:27   ` Alexandre Courbot [this message]
2025-12-08 23:17 ` [PATCH v3 05/12] gpu: nova-core: add NV_PFALCON_FALCON_DMATRFCMD::with_falcon_mem() Timur Tabi
2025-12-08 23:17 ` [PATCH v3 06/12] gpu: nova-core: add Turing boot registers Timur Tabi
2025-12-17  6:36   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 07/12] gpu: nova-core: move some functions into the HAL Timur Tabi
2025-12-08 23:17 ` [PATCH v3 08/12] gpu: nova-core: Add basic Turing HAL Timur Tabi
2025-12-17  6:40   ` Alexandre Courbot
2025-12-08 23:17 ` [PATCH v3 09/12] gpu: nova-core: add Falcon HAL method supports_dma() Timur Tabi
2025-12-08 23:17 ` [PATCH v3 10/12] gpu: nova-core: add FalconUCodeDescV2 support Timur Tabi
2025-12-08 23:18 ` [PATCH v3 11/12] gpu: nova-core: align LibosMemoryRegionInitArgument size to page size Timur Tabi
2025-12-17  7:17   ` Alexandre Courbot
2025-12-08 23:18 ` [PATCH v3 12/12] gpu: nova-core: add PIO support for loading firmware images Timur Tabi
2025-12-17  6:37 ` [PATCH v3 00/12] gpu: nova-core: add Turing support Alexandre Courbot

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=DF0A16OM1I4A.3HGXMFWBP34IF@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=lyude@redhat.com \
    --cc=nouveau-bounces@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=ttabi@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;
as well as URLs for NNTP newsgroup(s).