All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Timur Tabi <ttabi@nvidia.com>
Cc: Lyude Paul <lyude@redhat.com>, nouveau@lists.freedesktop.org
Subject: Re: [PATCH] drm/nouveau: always set RMDevidCheckIgnore for GSP-RM
Date: Sat, 9 Aug 2025 13:12:39 +0200	[thread overview]
Message-ID: <d35654eb-6aee-4b5d-88af-32bfe4eb6b5c@kernel.org> (raw)
In-Reply-To: <20250808191340.1701983-1-ttabi@nvidia.com>

On 8/8/25 9:13 PM, Timur Tabi wrote:
> Always set the RMDevidCheckIgnore registry key for GSP-RM so that it
> will continue support newer variants of already supported GPUs.
> 
> GSP-RM maintains an internal list of PCI IDs of GPUs that it supports,
> and checks if the current GPU is on this list.  While the actual GPU
> architecture (as specified in the BOOT_0/BOOT_42 registers) determines
> how to enable the GPU, the PCI ID is used for the product name, e.g.
> "NVIDIA GeForce RTX 5090".
> 
> Unfortunately, if there is no match, GSP-RM will refuse to initialize,
> even if the device is fully supported.  Nouveau will get an error
> return code, but by then it's too late.  This behavior may be corrected
> in a future version of GSP-RM, but that does not help Nouveau today.

Are there any GPUs in the field today which technically are supported, but yet
refused by GSP due to this?

> Fortunately, GSP-RM supports an undocumented registry key that tells it
> to ignore the mismatch.  In such cases, the product name returned will
> be a blank string, but otherwise GSP-RM will continue.

I assume you refer to internal documentation when you say "undocumented"?

> Unlike Nvidia's proprietary driver, Nouveau cannot update to newer
> firmware versions to keep up with every new hardware release.  Instead,
> we can permanently set this registry key, and GSP-RM will continue
> to function the same with known hardware.

  reply	other threads:[~2025-08-09 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 19:13 [PATCH] drm/nouveau: always set RMDevidCheckIgnore for GSP-RM Timur Tabi
2025-08-09 11:12 ` Danilo Krummrich [this message]
2025-08-11 17:28   ` Timur Tabi
2025-08-11 22:34 ` Danilo Krummrich

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=d35654eb-6aee-4b5d-88af-32bfe4eb6b5c@kernel.org \
    --to=dakr@kernel.org \
    --cc=lyude@redhat.com \
    --cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.