linux-kernel - Re: (subset) [PATCH 0/9] media: rkvdec: Add HEVC backend

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]

Date:   Mon,  6 Nov 2023 10:41:38 +0100
From:   Heiko Stuebner <heiko@...ech.de>
To:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Jonas Karlman <jonas@...boo.se>,
        Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
        Hans Verkuil <hverkuil-cisco@...all.nl>
Cc:     Heiko Stuebner <heiko@...ech.de>,
        Christopher Obbard <chris.obbard@...labora.com>,
        linux-staging@...ts.linux.dev,
        Benjamin Gaignard <benjamin.gaignard@...labora.com>,
        Nicolas Dufresne <nicolas.dufresne@...labora.com>,
        Alex Bee <knaerzche@...il.com>, linux-media@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Sebastian Fricke <sebastian.fricke@...labora.com>,
        linux-rockchip@...ts.infradead.org
Subject: Re: (subset) [PATCH 0/9] media: rkvdec: Add HEVC backend

On Sun, 5 Nov 2023 23:36:07 +0000, Jonas Karlman wrote:
> This series add a HEVC backend to the Rockchip Video Decoder driver.
> 
> A version of this HEVC backend has been in use by the LibreELEC distro
> for the past 3+ years [1]. It was initially created based on a copy of
> the H264 backend, unstable HEVC uAPI controls and a cabac table + scaling
> matrix functions shamelessly copied 1:1 from the Rockchip mpp library.
> 
> [...]

Applied as fix for 6.7-rc, thanks!

[8/9] arm64: dts: rockchip: Expand reg size of vdec node for RK3328
      commit: 667a89fe8383de1be44a8cdf22716448f84ee510
[9/9] arm64: dts: rockchip: Expand reg size of vdec node for RK3399
      commit: a31d776cccb98e0763dadce023ad5caa1a6dce2c

Expanding the range up to the start of the MMU should always be the
correct way, so this doesn't need the rest of the series :-) .


Best regards,
-- 
Heiko Stuebner <heiko@...ech.de>