From: amazingfate <liujianfeng1994@gmail.com>
To: jonas@kwiboo.se
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
ezequiel@vanguardiasur.com.ar, heiko@sntech.de,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org, liujianfeng1994@gmail.com,
mchehab@kernel.org, p.zabel@pengutronix.de, robh+dt@kernel.org,
sfr@canb.auug.org.au, sigmaris@gmail.com
Subject: Re: [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588
Date: Sat, 30 Dec 2023 23:31:59 +0800 [thread overview]
Message-ID: <20231230153159.3748580-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <97faf49b-0109-439a-accf-251b502ad40b@kwiboo.se>
Hi Jonas,
On Sat, 30 Dec 2023 12:49:38 +0100, Jonas Karlman <jonas@kwiboo.se> wrote:
>I have only tested this fork of fluster with ffmpeg 6.x, what version of
>ffmpeg did you test with? I was expecting it to also work on ffmpeg 5.x.
I am using ffmpeg 6.0 with v4l2-request patches from libreelec[1].
Ffmpeg v4l2 decoder in fluster fork is using ffmpeg args:
"-hwaccel_device /dev/dri/renderD128"
which make the test fall with hantro g1 on rk3588. After removing it I
can run tests by ffmpeg v4l2-request decoder.
Rk3566 and rk3588 are sharing the same results:
JVT-AVC_V1 test suite with decoder FFmpeg-H.264-V4L2-request:
Ran 127/135 tests successfully.
JVT-FR_EXT test suite with decoder FFmpeg-H.264-V4L2-request:
Ran 44/69 tests successfully.
VP8-TEST-VECTORS test suite with decoder FFmpeg-VP8-V4L2-request:
Ran 59/61 tests successfully.
[1] https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/multimedia/ffmpeg/patches/v4l2-request/ffmpeg-001-v4l2-request.patch
Regards,
Jianfeng
next prev parent reply other threads:[~2023-12-30 15:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 13:16 [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588 Jianfeng Liu
2023-12-28 13:16 ` [PATCH v2 1/3] media: verisilicon: Add support for Hantro G1 on RK3588 Jianfeng Liu
2023-12-28 13:16 ` [PATCH v2 2/3] arm64: dts: rockchip: Add Hantro G1 VPU support for RK3588 Jianfeng Liu
2023-12-29 11:02 ` Hugh Cole-Baker
2023-12-30 10:20 ` amazingfate
2023-12-28 13:16 ` [PATCH v2 3/3] dt-bindings: media: rockchip-vpu: Add RK3588 compatible Jianfeng Liu
2023-12-30 16:06 ` Krzysztof Kozlowski
2023-12-30 17:17 ` amazingfate
2023-12-29 11:01 ` [PATCH v2 0/3] Add hantro g1 video decoder support for RK3588 Hugh Cole-Baker
2023-12-30 9:52 ` amazingfate
2023-12-30 11:49 ` Jonas Karlman
2023-12-30 15:31 ` amazingfate [this message]
2023-12-30 20:12 ` Jonas Karlman
2023-12-30 9:46 ` Alex Bee
2023-12-30 10:03 ` amazingfate
2023-12-30 10:09 ` amazingfate
2023-12-30 17:23 ` amazingfate
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=20231230153159.3748580-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sigmaris@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;
as well as URLs for NNTP newsgroup(s).