All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Aaron Kling <webgeek1234@gmail.com>
Cc: linux-tegra@vger.kernel.org
Subject: Re: [REQUEST] Release Firmware to Match Current Driver Support
Date: Mon, 11 May 2026 17:02:10 +0900	[thread overview]
Message-ID: <78vIAjaWTgyGORO7lyOZcw@nvidia.com> (raw)
In-Reply-To: <CALHNRZ9152Ox=Y230zmFM_eywsOtr0Z07CYLKZH+hGbOhRmF7w@mail.gmail.com>

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



      reply	other threads:[~2026-05-11  8:02 UTC|newest]

Thread overview: 5+ 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 [this message]

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=78vIAjaWTgyGORO7lyOZcw@nvidia.com \
    --to=mperttunen@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --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 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.