From: Steve Longerbeam <slongerbeam@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-media <linux-media@vger.kernel.org>,
Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: Re: ADV7180 Capture with i.MX53
Date: Mon, 7 Oct 2019 17:51:26 -0700 [thread overview]
Message-ID: <ca2d67ed-9da1-7579-05d1-4c912bbf8093@gmail.com> (raw)
In-Reply-To: <CAOMZO5BRxvY2=8md7mo0ygsFXdrk2CVYrN_L5q-TQU_AhWCdgg@mail.gmail.com>
On 10/7/19 5:46 PM, Fabio Estevam wrote:
> Hi Steve,
>
> On Mon, Oct 7, 2019 at 9:37 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
>> The adv7180 driver in 5.3.x doesn't support seq-bt, only alternate. So
>> pad format should be "[fmt:UYVY2X8/720x240 field:alternate]".
> Thanks for the suggestion. After changing to field:alternate I get:
>
> # gst-launch-1.0 v4l2src ! fakesink
> Setting pipeline to PAUSED ...
> Pipeline is live and does not need PREROLL ...
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Device
> '/dev/video0' does not support progressive interlacing
Ah progress. Try:
v4l2-ctl -d0 --set-fmt-video=field=interlaced
Unless you specify interlaced at the video interface, the driver will
just combine alternate fields into seq-bt. I guess the v4l2src plugin
doesn't support seq-bt.
Steve
> Additional debug info:
> ../../../gst-plugins-good-1.14.4/sys/v4l2/gstv4l2object.c(3813):
> gst_v4l2_object_set_format_full ():
> /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
> Device wants interleaved interlacing
> Execution ended after 0:00:00.020459489
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> Setting pipeline to NULL ...
> Freeing pipeline ...
next prev parent reply other threads:[~2019-10-08 0:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 0:15 ADV7180 Capture with i.MX53 Fabio Estevam
2019-10-08 0:37 ` Steve Longerbeam
2019-10-08 0:46 ` Fabio Estevam
2019-10-08 0:51 ` Steve Longerbeam [this message]
2019-10-08 1:07 ` Fabio Estevam
2019-10-08 1:40 ` Fabio Estevam
2019-10-08 11:21 ` Fabio Estevam
2019-10-08 16:55 ` Tim Harvey
2019-10-08 17:14 ` Steve Longerbeam
2019-10-08 17:20 ` Ian Arkver
2019-10-08 17:30 ` Steve Longerbeam
2019-10-08 17:33 ` Ian Arkver
2019-10-08 20:34 ` Fabio Estevam
2019-10-08 21:01 ` Tim Harvey
2019-10-08 23:48 ` Fabio Estevam
2019-10-09 15:40 ` Tim Harvey
2019-10-09 17:22 ` Steve Longerbeam
2019-10-18 22:33 ` Matthew Starr
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=ca2d67ed-9da1-7579-05d1-4c912bbf8093@gmail.com \
--to=slongerbeam@gmail.com \
--cc=festevam@gmail.com \
--cc=linux-media@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox