From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-amlogic@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v5 0/5] media: meson: vdec: Add VP9 decoding support
Date: Mon, 02 Mar 2020 17:23:54 +0100 [thread overview]
Message-ID: <7h1rqasp2d.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140958.23542-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patchset aims to bring VP9 decoding support to Amlogic GXL, G12A & SM1
> platforms for the amlogic stateful video decoder driver.
>
> With this, it passes v4l2-compliance with streaming on Amlogic G12A and
> Amlogic SM1 SoCs successfully using the stream at [1] with a fixed
> pyv4l2compliance script for VP9 at [2].
>
> The original script kept the IVF headers in the stream, confusing the
> decoder. The fixed script only extracts the payload from the IVF container.
>
> The decoder has been tested using the Google CTS TestVectorsIttiam VP9 yuv420
> samples and the VP9 Decoder Performance streams at [5], decoding all streams from
> Profile 0 and 2 up to Level 4.1, with 10bit downsampling to 8bit.
Tested on meson-sm1-sei610,
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-amlogic@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v5 0/5] media: meson: vdec: Add VP9 decoding support
Date: Mon, 02 Mar 2020 17:23:54 +0100 [thread overview]
Message-ID: <7h1rqasp2d.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140958.23542-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patchset aims to bring VP9 decoding support to Amlogic GXL, G12A & SM1
> platforms for the amlogic stateful video decoder driver.
>
> With this, it passes v4l2-compliance with streaming on Amlogic G12A and
> Amlogic SM1 SoCs successfully using the stream at [1] with a fixed
> pyv4l2compliance script for VP9 at [2].
>
> The original script kept the IVF headers in the stream, confusing the
> decoder. The fixed script only extracts the payload from the IVF container.
>
> The decoder has been tested using the Google CTS TestVectorsIttiam VP9 yuv420
> samples and the VP9 Decoder Performance streams at [5], decoding all streams from
> Profile 0 and 2 up to Level 4.1, with 10bit downsampling to 8bit.
Tested on meson-sm1-sei610,
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-amlogic@lists.infradead.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v5 0/5] media: meson: vdec: Add VP9 decoding support
Date: Mon, 02 Mar 2020 17:23:54 +0100 [thread overview]
Message-ID: <7h1rqasp2d.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140958.23542-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patchset aims to bring VP9 decoding support to Amlogic GXL, G12A & SM1
> platforms for the amlogic stateful video decoder driver.
>
> With this, it passes v4l2-compliance with streaming on Amlogic G12A and
> Amlogic SM1 SoCs successfully using the stream at [1] with a fixed
> pyv4l2compliance script for VP9 at [2].
>
> The original script kept the IVF headers in the stream, confusing the
> decoder. The fixed script only extracts the payload from the IVF container.
>
> The decoder has been tested using the Google CTS TestVectorsIttiam VP9 yuv420
> samples and the VP9 Decoder Performance streams at [5], decoding all streams from
> Profile 0 and 2 up to Level 4.1, with 10bit downsampling to 8bit.
Tested on meson-sm1-sei610,
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
next prev parent reply other threads:[~2020-03-02 16:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:09 [PATCH v5 0/5] media: meson: vdec: Add VP9 decoding support Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` [PATCH v5 1/5] media: meson: vdec: align stride on 32 bytes Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` [PATCH v5 2/5] media: meson: vdec: add helpers for lossless framebuffer compression buffers Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` [PATCH v5 3/5] media: meson: vdec: add common HEVC decoder support Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` [PATCH v5 4/5] media: meson: vdec: add VP9 input support Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` [PATCH v5 5/5] media: meson: vdec: add VP9 decoder support Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-02-19 14:09 ` Neil Armstrong
2020-03-02 16:23 ` Kevin Hilman [this message]
2020-03-02 16:23 ` [PATCH v5 0/5] media: meson: vdec: Add VP9 decoding support Kevin Hilman
2020-03-02 16:23 ` Kevin Hilman
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=7h1rqasp2d.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.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.