From: Joel Fernandes <joelagnelf@nvidia.com>
To: Timur Tabi <ttabi@nvidia.com>,
"dakr@kernel.org" <dakr@kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Cc: Alistair Popple <apopple@nvidia.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
Eliot Courtney <ecourtney@nvidia.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aliceryhl@google.com" <aliceryhl@google.com>,
Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH] gpu: nova-core: require little endian
Date: Tue, 7 Apr 2026 14:30:13 -0400 [thread overview]
Message-ID: <f8229cdf-77bd-491c-b0ed-bbbe33156f1d@nvidia.com> (raw)
In-Reply-To: <6c0ca9e1e574635710ded3816bb9bd429c19dad3.camel@nvidia.com>
On 4/7/2026 2:02 PM, Timur Tabi wrote:
> On Tue, 2026-04-07 at 12:56 +0200, Danilo Krummrich wrote:
>> On Mon Apr 6, 2026 at 6:30 PM CEST, Joel Fernandes wrote:
>>> Nouveau does not do this, and no other GPU driver afaics either.
>>
>> Nouveau has nvkm_device_endianness() [1], which it configured before everything
>> else is done.
>>
>> I assume that's not an option for later GPUs?
>>
>> [1]
>> https://elixir.bootlin.com/linux/v6.19.11/source/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c#L3111
>
> Pascal is the last GPU to have NV_PMC_BOOT_1_ENDIAN0. If nvkm_device_endianness() is called on
> Turing, then that might be a bug.
Yes, this was on old/legacy GPUs, not GSP-based ones.
thanks,
--
Joel Fernandes
next prev parent reply other threads:[~2026-04-07 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 6:52 [PATCH] gpu: nova-core: require little endian Eliot Courtney
2026-04-06 16:30 ` Joel Fernandes
2026-04-07 10:56 ` Danilo Krummrich
2026-04-07 18:02 ` Timur Tabi
2026-04-07 18:30 ` Joel Fernandes [this message]
2026-04-06 16:34 ` Gary Guo
2026-04-06 19:37 ` John Hubbard
2026-04-06 19:46 ` Danilo Krummrich
2026-04-07 2:15 ` Eliot Courtney
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=f8229cdf-77bd-491c-b0ed-bbbe33156f1d@nvidia.com \
--to=joelagnelf@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=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox