linux-kernel - Re: [PATCH 0/3] NVIDIA Tegra210 NVJPG support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <96b721cd-7223-4b28-a3fd-a4d92c9d5142@tecnico.ulisboa.pt>
Date: Wed, 11 Jun 2025 13:05:40 +0100
From: Diogo Ivo <diogo.ivo@...nico.ulisboa.pt>
To: Mikko Perttunen <cyndis@...si.fi>,
 Thierry Reding <thierry.reding@...il.com>
Cc: Mikko Perttunen <mperttunen@...dia.com>, David Airlie
 <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
 Jonathan Hunter <jonathanh@...dia.com>,
 Philipp Zabel <p.zabel@...gutronix.de>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
 dri-devel@...ts.freedesktop.org, linux-tegra@...r.kernel.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH 0/3] NVIDIA Tegra210 NVJPG support



On 6/10/25 10:52 AM, Mikko Perttunen wrote:
> On 6/10/25 6:05 PM, Thierry Reding wrote:
>> On Fri, Jun 06, 2025 at 11:45:33AM +0100, Diogo Ivo wrote:
>>> Hello,
>>>
>>> This series adds support for the NVJPG hardware accelerator found in the
>>> Tegra210 SoC.
>>>
>>> The kernel driver is essentially a copy of the NVDEC driver as both
>>> engines are Falcon-based.
>>>
>>> For the userspace part I have written a Mesa Gallium backend [1] that,
>>> while still very much experimental, works in decoding images with VA- 
>>> API.
>>>
>>> I have been using ffmpeg to call VA-API with the following command:
>>>
>>> ffmpeg -v verbose -hwaccel vaapi -hwaccel_device /dev/dri/renderD129 
>>> -i <input.jpg> -pix_fmt bgra -f fbdev /dev/fb0
>>>
>>> which decodes <input.jpg> and shows the result in the framebuffer.
>>>
>>> The firmware for the engine can be obtained from a Linux for Tegra
>>> distribution.
>>
>> By the way, have you tried running this on anything newer than Tegra210?
>> Given your progress on this, we can probably start thinking about
>> submitting the binaries to linux-firmware.
> 
> FWIW, the impression I have is that NVJPG is basically unchanged all the 
> way to Tegra234. So if we add stream ID support and the firmwares, it'll 
> probably just work. Tegra234 has the quirk that it has two instances of 
> NVJPG -- these have to be distinguished by their different class IDs. 
> But we should go ahead with the T210 support first.

I have a question here, what exactly are the stream IDs? While working
on the driver this came up and I didn't manage to figure it out.

Diogo