linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Enrico <ebutera@users.sourceforge.net>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	stefan@herbrechtsmeier.net
Subject: Re: [PATCH 00/11] OMAP3 ISP BT.656 support
Date: Tue, 22 Jul 2014 18:32:05 +0200	[thread overview]
Message-ID: <2638081.aLalCDHyz1@avalon> (raw)
In-Reply-To: <CA+2YH7vNd4kC3=82M=UhHmNcXFGxBaiLUVbSkoXRvT8tfZkfcA@mail.gmail.com>

Hi Enrico,

On Tuesday 22 July 2014 18:26:52 Enrico wrote:
> On Tue, Jul 22, 2014 at 6:04 PM, Laurent Pinchart wrote:
> > Hi Enrico,
> > 
> > You will need to upgrade media-ctl and yavta to versions that support
> > interlaced formats. media-ctl has been moved to v4l-utils
> > (http://git.linuxtv.org/cgit.cgi/v4l-utils.git/) and yavta is hosted at
> > git://git.ideasonboard.org/yavta.git. You want to use the master branch
> > for both trees.
> 
> It seems that in v4l-utils there is no field support in media-ctl, am i
> wrong?

Oops, my bad, you're absolutely right.

> I forgot to add that i'm using yavta master and media-ctl "field"
> branch (from ideasonboard).

Could you please try media-ctl from

	git://linuxtv.org/pinchartl/v4l-utils.git field

The IOB repository is deprecated, although the version of media-ctl present 
there might work, I'd like to rule out that issue.

The media-ctl output you've posted doesn't show field information, so you're 
probably running either the wrong media-ctl version or the wrong kernel 
version.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-07-22 16:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 19:50 [PATCH 00/11] OMAP3 ISP BT.656 support Laurent Pinchart
2014-05-26 19:50 ` [PATCH 01/11] v4l: subdev: Extend default link validation to cover field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 02/11] omap3isp: Don't ignore subdev streamoff failures Laurent Pinchart
2014-05-26 19:50 ` [PATCH 03/11] omap3isp: Remove boilerplate disclaimer and FSF address Laurent Pinchart
2014-05-26 19:50 ` [PATCH 04/11] omap3isp: Move non-critical code out of the mutex-protected section Laurent Pinchart
2014-05-26 19:50 ` [PATCH 05/11] omap3isp: Default to progressive field order when setting the format Laurent Pinchart
2014-05-26 19:50 ` [PATCH 06/11] omap3isp: video: Validate the video node field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 07/11] omap3isp: ccdc: Simplify the configuration function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 08/11] omap3isp: ccdc: Simplify the ccdc_isr_buffer() function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 09/11] omap3isp: ccdc: Add basic support for interlaced video Laurent Pinchart
2014-05-26 21:12   ` Sakari Ailus
2014-05-26 19:50 ` [PATCH 10/11] omap3isp: ccdc: Support the interlaced field orders at the CCDC output Laurent Pinchart
2014-05-26 19:50 ` [PATCH 11/11] omap3isp: ccdc: Add support for BT.656 YUV format at the CCDC input Laurent Pinchart
2014-05-26 21:18 ` [PATCH 00/11] OMAP3 ISP BT.656 support Sakari Ailus
2014-05-27  8:38 ` Enrico
2014-06-24 15:19   ` Enrico
2014-06-24 17:19     ` Stefan Herbrechtsmeier
2014-07-01 20:24       ` Laurent Pinchart
2014-07-04 11:21         ` Stefan Herbrechtsmeier
2014-06-26 16:18     ` Enrico
2014-07-01 20:17       ` Laurent Pinchart
2014-07-22 15:52     ` Enrico
2014-07-22 16:04       ` Laurent Pinchart
2014-07-22 16:26         ` Enrico
2014-07-22 16:32           ` Laurent Pinchart [this message]
2014-07-23 13:54             ` Enrico
2014-07-23 13:57               ` Enrico
2014-07-30 21:01                 ` Laurent Pinchart
2014-07-31 10:21                   ` Enrico
2014-08-01 13:46                     ` Laurent Pinchart
     [not found]         ` <1406046034.73192.YahooMailNeo@web162404.mail.bf1.yahoo.com>
2014-07-22 16:27           ` Laurent Pinchart

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=2638081.aLalCDHyz1@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=eballetbo@gmail.com \
    --cc=ebutera@users.sourceforge.net \
    --cc=linux-media@vger.kernel.org \
    --cc=stefan@herbrechtsmeier.net \
    /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).