From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "John Hubbard" <jhubbard@nvidia.com>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Edwin Peer" <epeer@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>,
nouveau@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Nouveau <nouveau-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v8 5/6] gpu: nova-core: add boot42 support for next-gen GPUs
Date: Fri, 14 Nov 2025 23:01:41 +0900 [thread overview]
Message-ID: <DE8H17HDS2CL.2PKRL4FNPAXDJ@nvidia.com> (raw)
In-Reply-To: <20251114024109.465136-6-jhubbard@nvidia.com>
On Fri Nov 14, 2025 at 11:41 AM JST, John Hubbard wrote:
<snip>
> diff --git a/drivers/gpu/nova-core/regs.rs b/drivers/gpu/nova-core/regs.rs
> index 8c9af3c59708..81097e83c276 100644
> --- a/drivers/gpu/nova-core/regs.rs
> +++ b/drivers/gpu/nova-core/regs.rs
> @@ -41,14 +41,24 @@
> });
>
> impl NV_PMC_BOOT_0 {
> - /// Combines `architecture_0` and `architecture_1` to obtain the architecture of the chip.
> - pub(crate) fn architecture(self) -> Result<Architecture> {
> - Architecture::try_from(
> - self.architecture_0() | (self.architecture_1() << Self::ARCHITECTURE_0_RANGE.len()),
> - )
> + pub(crate) fn is_older_than_fermi(self) -> bool {
> + // From https://github.com/NVIDIA/open-gpu-doc/tree/master/manuals :
> + const NV_PMC_BOOT_0_ARCHITECTURE_GF100: u8 = 0xc;
> +
> + // Older chips left arch1 zeroed out. That, combined with an arch0 value that is less than
> + // GF100, means "older than Fermi".
> + self.architecture_1() == 0 && self.architecture_0() < NV_PMC_BOOT_0_ARCHITECTURE_GF100
> }
> +}
> +
> +register!(NV_PMC_BOOT_42 @ 0x00000a00, "Extended architecture information" {
> + 15:12 minor_revision as u8, "Minor revision of the chip";
> + 19:16 major_revision as u8, "Major revision of the chip";
> + 23:20 implementation as u8, "Implementation version of the architecture";
> + 29:24 architecture as u8 ?=> Architecture, "Architecture value";
> +});
>
> - /// Combines `architecture` and `implementation` to obtain a code unique to the chipset.
This comment for the `chipset` method got deleted. Is there a reason? If not I'll restore it when applying.
next prev parent reply other threads:[~2025-11-14 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:41 [PATCH v8 0/6] gpu: nova: add boot42 support for next-gen GPUs John Hubbard
2025-11-14 2:41 ` [PATCH v8 1/6] gpu: nova-core: implement Display for Spec John Hubbard
2025-11-14 15:18 ` Alexandre Courbot
2025-11-14 2:41 ` [PATCH v8 2/6] gpu: nova-core: prepare Spec and Revision types for boot0/boot42 John Hubbard
2025-11-14 14:37 ` Alexandre Courbot
2025-11-15 0:49 ` John Hubbard
2025-11-14 2:41 ` [PATCH v8 3/6] gpu: nova-core: make Architecture behave as a u8 type John Hubbard
2025-11-14 2:41 ` [PATCH v8 4/6] gpu: nova-core: use ENOTSUPP for unsupported GPUs, in all cases John Hubbard
2025-11-14 15:03 ` Alexandre Courbot
2025-11-14 23:41 ` John Hubbard
2025-11-14 2:41 ` [PATCH v8 5/6] gpu: nova-core: add boot42 support for next-gen GPUs John Hubbard
2025-11-14 14:01 ` Alexandre Courbot [this message]
2025-11-15 0:10 ` John Hubbard
2025-11-14 2:41 ` [PATCH v8 6/6] gpu: nova-core: provide a clear error report for unsupported GPUs John Hubbard
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=DE8H17HDS2CL.2PKRL4FNPAXDJ@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=epeer@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau-bounces@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).