From: "Danilo Krummrich" <dakr@kernel.org>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: Dave Airlie <airlied@redhat.com>, nouveau@lists.freedesktop.org
Subject: Re: [PATCH 0/6] drm/nouveau: fix GA100 issues
Date: Tue, 28 Apr 2026 17:07:12 +0200 [thread overview]
Message-ID: <DI4VR9K4MH1Z.IDI6P1QIS02O@kernel.org> (raw)
In-Reply-To: <20260407192122.3055293-1-ttabi@nvidia.com>
On Tue Apr 7, 2026 at 9:21 PM CEST, Timur Tabi wrote:
> Timur Tabi (6):
> drm/nouveau: check for GA100 specifically when calculating FRTS size
> drm/nouveau/bios: specify correct display fuse register for Ampere and
> Ada
> drm/nouveau/bios: skip the IFR header if present
> drm/nouveau/gsp: require GSP-RM for GA100 support
> drm/nouveau: parse the VBIOS on GA100
> drm/nouveau/gsp: enable FWSEC-SB on GA100
Hm...this is five times the size of the patch adding GA100 support in the first
place, i.e. it doesn't feel like -fixes material, but more like deferred -next
material.
Thus, can you please send a revert for commit 20e0c197802c ("drm/nouveau/gsp:
add support for GA100") and make this a new clean series adding GA100 support
for v7.2?
Thanks,
Danilo
next prev parent reply other threads:[~2026-04-28 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 19:21 [PATCH 0/6] drm/nouveau: fix GA100 issues Timur Tabi
2026-04-07 19:21 ` [PATCH 1/6] drm/nouveau: check for GA100 specifically when calculating FRTS size Timur Tabi
2026-04-07 19:21 ` [PATCH 2/6] drm/nouveau/bios: specify correct display fuse register for Ampere and Ada Timur Tabi
2026-04-07 19:21 ` [PATCH 3/6] drm/nouveau/bios: skip the IFR header if present Timur Tabi
2026-04-07 19:21 ` [PATCH 4/6] drm/nouveau/gsp: require GSP-RM for GA100 support Timur Tabi
2026-04-07 19:21 ` [PATCH 5/6] drm/nouveau: parse the VBIOS on GA100 Timur Tabi
2026-04-07 19:21 ` [PATCH 6/6] drm/nouveau/gsp: enable FWSEC-SB " Timur Tabi
2026-04-10 0:36 ` [PATCH 0/6] drm/nouveau: fix GA100 issues lyude
2026-04-28 15:07 ` Danilo Krummrich [this message]
2026-04-28 16:18 ` 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=DI4VR9K4MH1Z.IDI6P1QIS02O@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@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.