All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kepplinger <martink@posteo.de>
To: Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Re: platform: coda: how to use firmware-imx binary releases? / how to use VDOA on imx6?
Date: Thu, 05 Oct 2017 16:30:07 +0200	[thread overview]
Message-ID: <3eb6a9b35d891d04608c569b3286496e@posteo.de> (raw)
In-Reply-To: <1507212647.27175.25.camel@ndufresne.ca>

Am 05.10.2017 16:10 schrieb Nicolas Dufresne:
> Le jeudi 05 octobre 2017 à 13:54 +0200, Martin Kepplinger a écrit :
>> > This message is most likely just a result of the VDOA not supporting
>> > the
>> > selected capture format. In vdoa_context_configure, you can see that
>> > the
>> > VDOA only writes YUYV or NV12.
>> 
>> ok. I'll have to look into it, and just in case you see a problem on
>> first sight:
>> this is what coda says with debug level 1, when doing
>> 
>> gst-launch-1.0 playbin uri=file:///data/test2_hd480.h264
>> video-sink=fbdevsink
> 
> A bit unrelated, but kmssink remains a better choice here.
> 

True, but I'm currently not yet interested in the other end of the pipe 
:) Decoding
works in principal. VDOA is still disabled however :( I don't see what I 
can do
about this right now, which is a bit odd. It is definitely probed (and 
not removed).
I see at least a few frames of the video, so I guess the video file is 
fine? Or could
it be a file (or pixel) format that isn't supported? Again, ffprobe says

Stream #0:0: Video: h264 (High), yuv420p(progressive), 852x480, 24 fps, 
24 tbr, 1200k tbn, 48 tbc

                             thanks


After this, I want to have video conversion (color space) via a v4l2 
interface that
in turn uses the imx6 IPU. I guess gst-inspect-1.0 should see a V4L2 
Converter,
which it currently doesn't here:

# gst-inspect-1.0 | grep v4l2
video4linux2:  v4l2video1dec: V4L2 Video Decoder
video4linux2:  v4l2deviceprovider (GstDeviceProviderFactory)
video4linux2:  v4l2radio: Radio (video4linux2) Tuner
video4linux2:  v4l2sink: Video (video4linux2) Sink
video4linux2:  v4l2src: Video (video4linux2) Source

# dmesg | grep ipu
[    1.394717] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops 
0xc07d4b60)
[    1.402258] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops 
0xc07d4b60)
[    1.514984] imx-ipuv3 2400000.ipu: IPUv3H probed

should imx-ipuv3 provide a video4linux2 interface for video conversion? 
At least I don't
see it yet. (or other V4L2 Linux config options than I already have 
enabled)

  reply	other threads:[~2017-10-05 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  8:44 platform: coda: how to use firmware-imx binary releases? Martin Kepplinger
2017-10-04  9:22 ` Philipp Zabel
2017-10-05  7:43   ` Martin Kepplinger
2017-10-05  8:19     ` Philipp Zabel
2017-10-05 11:54       ` platform: coda: how to use firmware-imx binary releases? / how to use VDOA on imx6? Martin Kepplinger
2017-10-05 14:10         ` Nicolas Dufresne
2017-10-05 14:30           ` Martin Kepplinger [this message]
2017-10-05 15:45 ` platform: coda: how to use firmware-imx binary releases? Philipp Zabel
2017-10-05 16:00   ` Martin Kepplinger

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=3eb6a9b35d891d04608c569b3286496e@posteo.de \
    --to=martink@posteo.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    /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.