From: John Hubbard <jhubbard@nvidia.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: Danilo Krummrich <dakr@kernel.org>,
M Henning <mhenning@darkrefraction.com>,
nova-gpu <nova-gpu@lists.linux.dev>,
Alice Ryhl <aliceryhl@google.com>,
David Airlie <airlied@gmail.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Benno Lossin <lossin@kernel.org>, Gary Guo <gary@garyguo.net>,
Eliot Courtney <ecourtney@nvidia.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v4 3/7] drm: nova: Add chipid enum to nova-drm UAPI
Date: Tue, 25 Aug 2026 18:41:41 -0700 [thread overview]
Message-ID: <9ff4d5cd-527e-44dc-b42f-ebadfcaa5c7f@nvidia.com> (raw)
In-Reply-To: <ao48Kz_vDm8Ogg9n@nvdebian.thelocal>
On 8/25/26 6:27 PM, Alistair Popple wrote:
> On 2026-08-26 at 07:13 +1000, John Hubbard <jhubbard@nvidia.com> wrote...
>> On 8/25/26 1:53 PM, Danilo Krummrich wrote:
>>> On Tue Aug 25, 2026 at 9:13 AM CEST, Alistair Popple wrote:
>> ...
> Sure. Two questions:
>
> 1) Do we also need to provide the decoded implementation value?
User space needs to:
a) Know enough about the GPU to be able to choose an SM version (and
probably a few other things) which in turn is eventually required in
order to run GPU programs, as shown in your merge request[1].
b) Display GPU information to the user.
c) I'm sure to be overlooking something.
> 2) If we provide the decoded values why do we need to expose the chip-id at all?
OK, so maybe we don't?
[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/43352/diffs?commit_id=945a8e7c51939577526974b342c8dc6bafc3372f#3bb2fa8303917a2ad83e2239c2cae842dfaa594f
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-08-26 1:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 5:06 [PATCH v4 0/7] gpu: nova: Export parameters from nova-core to nova-drm Alistair Popple
2026-08-11 5:06 ` [PATCH v4 1/7] gpu: nova-core: Add public driver API to nova-core Alistair Popple
2026-08-11 5:06 ` [PATCH v4 2/7] drm: nova: Add DRM registration data Alistair Popple
2026-08-11 5:06 ` [PATCH v4 3/7] drm: nova: Add chipid enum to nova-drm UAPI Alistair Popple
2026-08-24 14:49 ` M Henning
2026-08-24 19:24 ` Danilo Krummrich
2026-08-25 7:13 ` Alistair Popple
2026-08-25 12:03 ` Alistair Popple
2026-08-25 20:53 ` Danilo Krummrich
2026-08-25 20:53 ` Danilo Krummrich
2026-08-25 21:13 ` John Hubbard
2026-08-26 1:27 ` Alistair Popple
2026-08-26 1:41 ` John Hubbard [this message]
2026-08-26 1:49 ` Alistair Popple
2026-08-11 5:06 ` [PATCH v4 4/7] drm: nova: Add a GPU info ioctl Alistair Popple
2026-08-17 20:18 ` Danilo Krummrich
2026-08-21 5:10 ` Alistair Popple
2026-08-24 19:10 ` Danilo Krummrich
2026-08-25 7:32 ` Alistair Popple
2026-08-25 22:37 ` Danilo Krummrich
2026-08-24 19:34 ` Danilo Krummrich
2026-08-24 20:04 ` John Hubbard
2026-08-25 6:40 ` Alistair Popple
2026-08-11 5:06 ` [PATCH v4 5/7] drm: nova: Add usable VRAM size to " Alistair Popple
2026-08-11 5:06 ` [PATCH v4 6/7] drm: nova: Use nova-core to read VRAM_BAR_SIZE parameter Alistair Popple
2026-08-17 20:11 ` Danilo Krummrich
2026-08-21 5:13 ` Alistair Popple
2026-08-11 5:06 ` [PATCH v4 7/7] drm: nova: Expose a render node Alistair Popple
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=9ff4d5cd-527e-44dc-b42f-ebadfcaa5c7f@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mhenning@darkrefraction.com \
--cc=nova-gpu@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
/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