linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: ezequiel@collabora.com, mchehab@kernel.org,
	Shawn Guo <shawnguo@kernel.org>,
	s.hauer@pengutronix.de,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org
Subject: video decoding on imx8mq vpu via v4l2
Date: Fri, 14 Feb 2020 12:46:38 +0100	[thread overview]
Message-ID: <ce102c01-74b1-628d-2192-9d5cb7baa616@puri.sm> (raw)

Hi,

I'd like to test decoding an mpeg2 or h264 video file on imx8mq, using
its vpu:

I use Philipp's changes for imx8m from
https://git.pengutronix.de/cgit/pza/linux/log/?h=hantro/imx8m-wip in my
tree:

https://source.puri.sm/martin.kepplinger/linux-next/commits/5.6-rc1/librem5__integration

and play around with gstreamer, taking notes at
https://source.puri.sm/Librem5/linux-next/issues/74

The driver probes fine and v4l2 appearently sees the MEM2MEM decoder:

$ v4l2-ctl --list-devices
nxp,imx8mq-vpu-dec (platform: hantro-vpu):
	/dev/video0


AFAIK gstreamer should provide a "v4l2videodec" element which it doesn't:

$ gst-inspect-1.0|grep -i v4l
video4linux2:  v4l2deviceprovider (GstDeviceProviderFactory)
video4linux2:  v4l2radio: Radio (video4linux2) Tuner
video4linux2:  v4l2sink: Video (video4linux2) Sink
video4linux2:  v4l2src: Video (video4linux2) Source


First: Philipp, do you plan to continue working on supporting hantro for
imx8m upstream?

Then: What codec would be appropriate to test decoding now? It seems
like h264 is supposed to be implemented. How do you test?

And finally: What could be missing here? I use debian's gstreamer
package, but in this case it can't really be a config/build issue in
gstreamer, right?

thanks,

                                martin

             reply	other threads:[~2020-02-14 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 11:46 Martin Kepplinger [this message]
2020-02-14 13:50 ` video decoding on imx8mq vpu via v4l2 Philipp Zabel
2020-02-22 16:16   ` +1 514-466-1652

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=ce102c01-74b1-628d-2192-9d5cb7baa616@puri.sm \
    --to=martin.kepplinger@puri.sm \
    --cc=ezequiel@collabora.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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 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).