From: John Hubbard <jhubbard@nvidia.com>
To: Timur Tabi <ttabi@nvidia.com>, Alexandre Courbot <acourbot@nvidia.com>
Cc: "gary@garyguo.net" <gary@garyguo.net>,
Eliot Courtney <ecourtney@nvidia.com>,
"nova-gpu@lists.linux.dev" <nova-gpu@lists.linux.dev>,
Zhi Wang <zhiw@nvidia.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"dakr@kernel.org" <dakr@kernel.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"driver-core@lists.linux.dev" <driver-core@lists.linux.dev>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"russ.weight@linux.dev" <russ.weight@linux.dev>
Subject: Re: [PATCH v3 5/7] gpu: nova-core: transition gen_bootloader to TLV images
Date: Thu, 9 Jul 2026 15:29:34 -0700 [thread overview]
Message-ID: <fb1d6ebb-cb45-442e-bfcb-73d3ba82fbb6@nvidia.com> (raw)
In-Reply-To: <6cb2d2292131615c44e03283092724a11b9e5619.camel@nvidia.com>
On 7/9/26 3:13 PM, Timur Tabi wrote:
> On Thu, 2026-07-09 at 14:49 -0700, John Hubbard wrote:
>>> I'm going to post a v4 today in the meantime.
>>
>> If you have a spec, then it's either a spec or it's just a waste of time.
>
> That's a little harsh. I was thinking that maybe we should change the spec instead, to specify
> that if the TLV references a version firmware image, then it should have a VERS tag.
oh sorry about sounding harsh. I'm trying to communicate that specs
are harsh. Because they are.
>
>> Assuming that it's a spec, then if it says "shall have a VERS tag", then
>> by gosh we should fail out if that tag is missing.
>>
>> Otherwise, write the spec differently.
>>
>> This is not a fuzzy sort of thing.
>
> I thought this was a forum for discussing things?
Yes, sorry again, the idea here is that specs are not fuzzy. I'm
not trying to quash discussion, just trying to say that if you have
a spec, then you either have to change the spec, or *follow it*.
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-07-09 22:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 19:27 [PATCH v3 0/7] Transition Nova Core to TLV firmare images Timur Tabi
2026-07-02 19:27 ` [PATCH v3 1/7] rust: firmware: add request_into_buf() Timur Tabi
2026-07-03 2:51 ` Alvin Sun
2026-07-03 3:06 ` Timur Tabi
2026-07-03 13:51 ` Danilo Krummrich
2026-07-06 6:30 ` Alexandre Courbot
2026-07-06 10:50 ` Danilo Krummrich
2026-07-07 2:54 ` Timur Tabi
2026-07-07 5:10 ` Alexandre Courbot
2026-07-07 13:32 ` Danilo Krummrich
2026-07-02 19:27 ` [PATCH v3 2/7] gpu: nova-core: add TLV parser for firmware files Timur Tabi
2026-07-02 19:45 ` Timur Tabi
2026-07-06 6:31 ` Alexandre Courbot
2026-07-07 2:56 ` Timur Tabi
2026-07-07 5:13 ` Alexandre Courbot
2026-07-08 22:48 ` Timur Tabi
2026-07-09 3:43 ` Alexandre Courbot
2026-07-09 21:29 ` Timur Tabi
2026-07-06 6:31 ` Alexandre Courbot
2026-07-08 20:12 ` Timur Tabi
2026-07-09 1:55 ` Alexandre Courbot
2026-07-02 19:27 ` [PATCH v3 3/7] gpu: nova-core: transition booter_load to TLV images Timur Tabi
2026-07-06 6:31 ` Alexandre Courbot
2026-07-08 20:46 ` Timur Tabi
2026-07-09 3:51 ` Alexandre Courbot
2026-07-09 21:31 ` Timur Tabi
2026-07-02 19:27 ` [PATCH v3 4/7] gpu: nova-core: transition gsp " Timur Tabi
2026-07-02 19:27 ` [PATCH v3 5/7] gpu: nova-core: transition gen_bootloader " Timur Tabi
2026-07-06 6:31 ` Alexandre Courbot
2026-07-08 22:26 ` Timur Tabi
2026-07-09 2:24 ` Alexandre Courbot
2026-07-09 21:27 ` Timur Tabi
2026-07-09 21:49 ` John Hubbard
2026-07-09 22:13 ` Timur Tabi
2026-07-09 22:29 ` John Hubbard [this message]
2026-07-09 22:39 ` Timur Tabi
2026-07-09 22:41 ` John Hubbard
2026-07-09 22:44 ` Timur Tabi
2026-07-02 19:27 ` [PATCH v3 6/7] gpu: nova-core: transition fsp " Timur Tabi
2026-07-02 19:27 ` [PATCH v3 7/7] gpu: nova-core: update firmware module info for " 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=fb1d6ebb-cb45-442e-bfcb-73d3ba82fbb6@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=mcgrof@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--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