From: Timur Tabi <ttabi@nvidia.com>
To: "airlied@gmail.com" <airlied@gmail.com>,
"pvorel@suse.cz" <pvorel@suse.cz>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"dakr@kernel.org" <dakr@kernel.org>
Subject: Re: [PATCH] nouveau: add option to avoid 535 firmware in initramfs
Date: Wed, 8 Oct 2025 03:18:22 +0000 [thread overview]
Message-ID: <4d706ee978f0e975e5bb99e2ea342fedfbac214b.camel@nvidia.com> (raw)
In-Reply-To: <CAPM=9tz_fnRxZm74C+JuxZjCbGEH66JbabN012zVNgKucrw8oA@mail.gmail.com>
On Wed, 2025-10-08 at 11:48 +1000, Dave Airlie wrote:
> I think that is getting a bit complicated for distros though. There is
> no reason to ever want 535 only. We don't want to give people options
> we don't actually support.
My Ubuntu 25.04 system ships with kernel 6.14 but only the r535 firmware. So there systems out
there with recent kernels that would select 535-only.
> The options we have in the current driver, is you get 535 + 570, and
> we give you the option to say I only need 570. If we add 580, we add
> another option and fix it then, but I don't see the point in
> overdesigning this for now.
Well, like you said, if we move to 580, then now we need to decide between 570 and 580. So
let's set up a Kconfig system that handles multiple versions in a future-proof way.
next prev parent reply other threads:[~2025-10-08 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 1:32 [PATCH] nouveau: add option to avoid 535 firmware in initramfs Dave Airlie
2025-10-07 3:29 ` Timur Tabi
2025-10-07 3:31 ` Dave Airlie
2025-10-07 3:41 ` Timur Tabi
2025-10-07 15:20 ` Petr Vorel
2025-10-08 1:48 ` Dave Airlie
2025-10-08 3:18 ` Timur Tabi [this message]
2025-10-08 3:43 ` Dave Airlie
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=4d706ee978f0e975e5bb99e2ea342fedfbac214b.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
--cc=pvorel@suse.cz \
/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.