From: Mikko Perttunen <mperttunen@nvidia.com>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-tegra@vger.kernel.org
Subject: Re: [REQUEST] Release Firmware to Match Current Driver Support
Date: Wed, 14 Oct 2026 16:35:54 +0900 [thread overview]
Message-ID: <zTfGVn53QmqQRM9wpFd_XQ@nvidia.com> (raw)
In-Reply-To: <CALHNRZ-nBgurVhtHjRtz0W0u1oNJY2eQo7xRA6kaUPyfZv9hcQ@mail.gmail.com>
On Wednesday, October 14, 2026 11:47 AM Aaron Kling wrote:
> On Tue, Oct 13, 2026 at 3:51 AM Mikko Perttunen <mperttunen@nvidia.com> wrote:
> >
> > On Tuesday, October 13, 2026 5:49 PM Mikko Perttunen wrote:
> > > On Tuesday, August 18, 2026 7:49 PM Thierry Reding wrote:
> > > > On Mon, Aug 17, 2026 at 12:17:27PM -0500, Aaron Kling wrote:
> > > > > On Mon, May 11, 2026 at 3:02 AM Mikko Perttunen <mperttunen@nvidia.com> wrote:
> > > > > >
> > > > > > On Monday, May 11, 2026 12:05 PM Aaron Kling wrote:
> > > > > > > On Fri, Nov 14, 2025 at 2:17 PM Aaron Kling <webgeek1234@gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Fri, Aug 1, 2025 at 4:56 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > On Thu, Jul 31, 2025 at 04:22:32PM -0500, Aaron Kling wrote:
> > > > > > > > > > This was originally discussed on the freedesktop issue tracker [0],
> > > > > > > > > > but there hasn't been a response there in 6 months. So I'm reopening
> > > > > > > > > > the discussion here.
> > > > > > > > > >
> > > > > > > > > > * Nvdec firmware. The driver has been in the kernel for over three
> > > > > > > > > > years and there's still no available freely licensed firmware to use
> > > > > > > > > > with it.
> > > > > > > > > > * T234 vic firmware. The driver has supported the arch for almost
> > > > > > > > > > three years and freely licensed firmware still isn't available.
> > > > > > > > > > * Nvjpg firmware. The driver is awaiting final approval, probably
> > > > > > > > > > worth it to release the firmware with everything else.
> > > > > > > > > >
> > > > > > > > > > * T194 nouveau firmware. This does not have driver support, but there
> > > > > > > > > > has been some interest in working on it. Making the firmware
> > > > > > > > > > available, even if it isn't merged to linux-firmware, would be one
> > > > > > > > > > less blocker for someone that doesn't work at Nvidia to work on
> > > > > > > > > > support.
> > > > > > > > > >
> > > > > > > > > > Aaron Kling
> > > > > > > > > >
> > > > > > > > > > [0] https://gitlab.freedesktop.org/drm/tegra/-/issues/4
> > > > > > > > >
> > > > > > > > > I will continue to look into this, but it'll not be high priority. Too
> > > > > > > > > many other things going on.
> > > > > > > >
> > > > > > > > After some discussion with nouveau developers, it was pointed out to
> > > > > > > > me that the gsp on ga10b doesn't do much and the setup is more like
> > > > > > > > prior tegra gpus. And that it wouldn't make sense to support ga10b on
> > > > > > > > nova. So I would like to expand the request for gv11b nouveau firmware
> > > > > > > > to also include ga10b. Perhaps not directly pushed to linux-firmware
> > > > > > > > until they can be verified working, but made available so driver
> > > > > > > > development can happen.
> > > > > > >
> > > > > > > It has been over eight months since the last response. Nvjpg driver
> > > > > > > support has been merged in the meantime. Has any progress been made on
> > > > > > > any of the firmware releases?
> > > > > > >
> > > > > > > Aaron
> > > > > >
> > > > > > I have the multimedia engine firmware files on my todo-list. I'm
> > > > > > planning to send these out after Tegra264 VIC support is ready to send.
> > > > > > Unfortunately there have been some delays in that.
> > > > > >
> > > > > > Mikko
> > > > >
> > > > > The Tegra264 VIC series has been picked up into -next. Is there any
> > > > > update on the firmware release process?
> > > >
> > > > We're still working on it, it's just taking a really long time.
> > > >
> > > > Thierry
> > >
> > > Firmware files for VIC, NVDEC, NVENC, NVJPG, OFA, and XUSB for Tegra124
> > > and later are now in linux-firmware:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=bdeb9f0f93f18d10b281217e66e81838527ce55a
> > >
> > > Thanks for your patience. I was about to lose mine a few times.
>
> Awesome. Thank you very much for keeping at this and getting it done.
>
> > > Mikko
> > >
> > >
> > >
> >
> > I'd like to add that I'm looking at GV11B and GA10B support and
> > associated firmware as well.
>
> Oh, nice. I've got t194 in fairly decent shape except for the gpu.
> Getting nouveau support would push that into a very viable state. T234
> is still giving me some trouble, but it's not too far off either.
If you have any issues I can help with please let me know.
>
> A related question here, for future planning: The soc in the upcoming
> Jetson Orin Nano 2, does that have ga10b or something compatible with
> the firmware? And is the existing t234 media firmware compatible? Or
> will there need to be a new release for that with matching driver
> compatible additions? I would really like to get mainline support
> going on that as soon as it's available.
Unfortunately I cannot comment on any specifics of the Nano 2 yet, but
we are working to get mainline support as quickly as possible.
Mikko
>
> Aaron
next prev parent reply other threads:[~2026-10-14 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 21:22 [REQUEST] Release Firmware to Match Current Driver Support Aaron Kling
2025-08-01 9:56 ` Thierry Reding
2025-11-14 20:17 ` Aaron Kling
2026-05-11 3:05 ` Aaron Kling
2026-05-11 8:02 ` Mikko Perttunen
2026-08-17 17:17 ` Aaron Kling
2026-08-18 10:49 ` Thierry Reding
2026-10-13 8:49 ` Mikko Perttunen
2026-10-13 8:51 ` Mikko Perttunen
2026-10-14 2:47 ` Aaron Kling
2026-10-14 7:35 ` Mikko Perttunen [this message]
2026-10-13 15:56 ` Thierry Reding
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=zTfGVn53QmqQRM9wpFd_XQ@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@kernel.org \
--cc=webgeek1234@gmail.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