All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: mchehab@samsung.com, linux-media@vger.kernel.org, hverkuil@xs4all.nl
Cc: matsu@igel.co.jp, linux-sh@vger.kernel.org,
	vladimir.barinov@cogentembedded.com
Subject: Re: [PATCH] ml86v7667: override default field interlace order
Date: Sat, 27 Jul 2013 22:20:48 +0000	[thread overview]
Message-ID: <51F447C0.9030901@cogentembedded.com> (raw)
In-Reply-To: <201307152312.22371.sergei.shtylyov@cogentembedded.com>

Hello.

On 15.07.2013 23:12, I wrote:

> From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>

> ML86V7667 always transmits top field first for both PAL and  NTSC -- that makes
> application incorrectly  treat interlaced  fields when relying on the standard.
> Hence we must set V4L2_FIELD_INTERLACED_TB format explicitly.

> Reported-by: Katsuya MATSUBARA <matsu@igel.co.jp>
> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> [Sergei: added a comment.]
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

> ---
> This patch is against the 'media_tree.git' repo.

    I forgot to mention that it was against the 'fixes' branch, and we 
intended it as a fix (I'm seeing this patch committed to the 'master' branch).

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: mchehab@samsung.com, linux-media@vger.kernel.org, hverkuil@xs4all.nl
Cc: matsu@igel.co.jp, linux-sh@vger.kernel.org,
	vladimir.barinov@cogentembedded.com
Subject: Re: [PATCH] ml86v7667: override default field interlace order
Date: Sun, 28 Jul 2013 02:20:48 +0400	[thread overview]
Message-ID: <51F447C0.9030901@cogentembedded.com> (raw)
In-Reply-To: <201307152312.22371.sergei.shtylyov@cogentembedded.com>

Hello.

On 15.07.2013 23:12, I wrote:

> From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>

> ML86V7667 always transmits top field first for both PAL and  NTSC -- that makes
> application incorrectly  treat interlaced  fields when relying on the standard.
> Hence we must set V4L2_FIELD_INTERLACED_TB format explicitly.

> Reported-by: Katsuya MATSUBARA <matsu@igel.co.jp>
> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> [Sergei: added a comment.]
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

> ---
> This patch is against the 'media_tree.git' repo.

    I forgot to mention that it was against the 'fixes' branch, and we 
intended it as a fix (I'm seeing this patch committed to the 'master' branch).

WBR, Sergei


  parent reply	other threads:[~2013-07-27 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 19:12 [PATCH] ml86v7667: override default field interlace order Sergei Shtylyov
2013-07-15 19:12 ` Sergei Shtylyov
2013-07-25  7:32 ` Katsuya MATSUBARA
2013-07-25  7:32   ` Katsuya MATSUBARA
2013-07-27 22:20 ` Sergei Shtylyov [this message]
2013-07-27 22:20   ` Sergei Shtylyov

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=51F447C0.9030901@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=matsu@igel.co.jp \
    --cc=mchehab@samsung.com \
    --cc=vladimir.barinov@cogentembedded.com \
    /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.