linux-kernel - Re: [PATCH 1/3] media: rockchip: Introduce the rkvdec2 driver

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: <171D4C9F-AA88-4DC5-87F2-142D642ECACE@gmail.com>
Date: Thu, 30 Jan 2025 11:22:26 +0100
From: Piotr Oniszczuk <piotr.oniszczuk@...il.com>
To: Nicolas Dufresne <nicolas@...fresne.ca>
Cc: Detlev Casanova <detlev.casanova@...labora.com>,
 linux-kernel@...r.kernel.org,
 Diederik de Haas <didi.debian@...ow.org>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Heiko Stuebner <heiko@...ech.de>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Sebastian Reichel <sebastian.reichel@...labora.com>,
 Dragan Simic <dsimic@...jaro.org>,
 Alexey Charkov <alchark@...il.com>,
 Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
 Andy Yan <andy.yan@...k-chips.com>,
 linux-media@...r.kernel.org,
 devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org,
 linux-rockchip@...ts.infradead.org,
 linux-staging@...ts.linux.dev
Subject: Re: [PATCH 1/3] media: rockchip: Introduce the rkvdec2 driver



> Wiadomość napisana przez Nicolas Dufresne <nicolas@...fresne.ca> w dniu 29 sty 2025, o godz. 17:20:
> 
> Hi Piotr,
> 
> Le mercredi 29 janvier 2025 à 15:48 +0100, Piotr Oniszczuk a écrit :
>> 
> 
> As for most codec, when working with larger group of developpers, its better to
> start with getting the ITU conformance tests passing. Once we reach an excellant
> score then we can start looking at specific streams. The benefit is that ITU
> conformance can be run with fluster which removes a lot of possible human
> errors.
> 

Ah indeed.
ITU conformance approach is for sure best one.

By asking for way/tool to analyse of playing/failing samples I was just curious: is there any pattern here (e.g. specific encoding mode; etc).
I assumed - it there is - this might be good pointer in narrowing decoder code which needs fixing.