From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-media@vger.kernel.org,
Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: acourbot@chromium.org, tfiga@chromium.org,
hverkuil-cisco@xs4all.nl,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
"moderated list:ARM/Allwinner sunXi SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Allwinner sunXi SoC support"
<linux-sunxi@lists.linux.dev>
Subject: Re: [RFC PATCH v3 1/2] media: docs-rst: Append HEVC specific term
Date: Mon, 28 Mar 2022 19:10:15 +0200 [thread overview]
Message-ID: <2095465.irdbgypaU6@jernej-laptop> (raw)
In-Reply-To: <20220327084308.9053-2-sebastian.fricke@collabora.com>
Dne nedelja, 27. marec 2022 ob 10:43:08 CEST je Sebastian Fricke napisal(a):
> Describe the coding tree unit as replacement for the macroblock in the
> HEVC codec. Highlight a key difference of the HEVC codec to predecessors
> like AVC(H.264) to give a better overview of the differences between the
> coding standards.
>
Looks good to me.
Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com>
> ---
> Documentation/userspace-api/media/v4l/dev-decoder.rst | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/media/v4l/dev-decoder.rst
> b/Documentation/userspace-api/media/v4l/dev-decoder.rst index
> 3cf2b496f2d0..eb5b1b1e3a51 100644
> --- a/Documentation/userspace-api/media/v4l/dev-decoder.rst
> +++ b/Documentation/userspace-api/media/v4l/dev-decoder.rst
> @@ -72,6 +72,11 @@ coded resolution
> coded width
> width for given coded resolution.
>
> +coding tree unit
> + processing unit of the HEVC codec (≘ macroblock units in H.264, VP8,
> VP9); + can use block structures of up to 64×64 pixels;
> + Good at sub-partitioning the picture into variable sized structures.
> +
> decode order
> the order in which frames are decoded; may differ from display order if
> the coded format includes a feature of frame reordering; for decoders, @@
> -104,7 +109,8 @@ keyframe
> macroblock
> a processing unit in image and video compression formats based on linear
> block transforms (e.g. H.264, VP8, VP9); codec-specific, but for most of -
> popular codecs the size is 16x16 samples (pixels).
> + popular codecs the size is 16x16 samples (pixels). The HEVC codec uses a
> + slightly more flexible processing unit called coding tree unit (CTU).
>
> OUTPUT
> the source buffer queue; for decoders, the queue of buffers containing
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-media@vger.kernel.org,
Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: acourbot@chromium.org, tfiga@chromium.org,
hverkuil-cisco@xs4all.nl,
Sebastian Fricke <sebastian.fricke@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
"moderated list:ARM/Allwinner sunXi SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Allwinner sunXi SoC support"
<linux-sunxi@lists.linux.dev>
Subject: Re: [RFC PATCH v3 1/2] media: docs-rst: Append HEVC specific term
Date: Mon, 28 Mar 2022 19:10:15 +0200 [thread overview]
Message-ID: <2095465.irdbgypaU6@jernej-laptop> (raw)
In-Reply-To: <20220327084308.9053-2-sebastian.fricke@collabora.com>
Dne nedelja, 27. marec 2022 ob 10:43:08 CEST je Sebastian Fricke napisal(a):
> Describe the coding tree unit as replacement for the macroblock in the
> HEVC codec. Highlight a key difference of the HEVC codec to predecessors
> like AVC(H.264) to give a better overview of the differences between the
> coding standards.
>
Looks good to me.
Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com>
> ---
> Documentation/userspace-api/media/v4l/dev-decoder.rst | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/media/v4l/dev-decoder.rst
> b/Documentation/userspace-api/media/v4l/dev-decoder.rst index
> 3cf2b496f2d0..eb5b1b1e3a51 100644
> --- a/Documentation/userspace-api/media/v4l/dev-decoder.rst
> +++ b/Documentation/userspace-api/media/v4l/dev-decoder.rst
> @@ -72,6 +72,11 @@ coded resolution
> coded width
> width for given coded resolution.
>
> +coding tree unit
> + processing unit of the HEVC codec (≘ macroblock units in H.264, VP8,
> VP9); + can use block structures of up to 64×64 pixels;
> + Good at sub-partitioning the picture into variable sized structures.
> +
> decode order
> the order in which frames are decoded; may differ from display order if
> the coded format includes a feature of frame reordering; for decoders, @@
> -104,7 +109,8 @@ keyframe
> macroblock
> a processing unit in image and video compression formats based on linear
> block transforms (e.g. H.264, VP8, VP9); codec-specific, but for most of -
> popular codecs the size is 16x16 samples (pixels).
> + popular codecs the size is 16x16 samples (pixels). The HEVC codec uses a
> + slightly more flexible processing unit called coding tree unit (CTU).
>
> OUTPUT
> the source buffer queue; for decoders, the queue of buffers containing
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-28 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 8:43 [RFC PATCH v3 0/2] HEVC enhancements Sebastian Fricke
2022-03-27 8:43 ` Sebastian Fricke
2022-03-27 8:43 ` [RFC PATCH v3 1/2] media: docs-rst: Append HEVC specific term Sebastian Fricke
2022-03-27 8:43 ` Sebastian Fricke
2022-03-28 17:10 ` Jernej Škrabec [this message]
2022-03-28 17:10 ` Jernej Škrabec
2022-03-27 8:43 ` [RFC PATCH v3 2/2] staging: media: cedrus: Rename H265 to HEVC Sebastian Fricke
2022-03-27 8:43 ` Sebastian Fricke
2022-03-28 17:09 ` Jernej Škrabec
2022-03-28 17:09 ` Jernej Škrabec
2022-03-29 6:53 ` Sebastian Fricke
2022-03-29 6:53 ` Sebastian Fricke
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=2095465.irdbgypaU6@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=acourbot@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=sebastian.fricke@collabora.com \
--cc=tfiga@chromium.org \
--cc=wens@csie.org \
/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.