All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert William Fuller <hydrologiccycle@gmail.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: v4l-dvb-maintainer@linuxtv.org, video4linux-list@redhat.com,
	Jean Delvare <jdelvare@suse.de>
Subject: Re: [v4l-dvb-maintainer] bttv driver questions
Date: Tue, 26 Aug 2008 22:59:52 -0400	[thread overview]
Message-ID: <48B4C328.2040502@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0808261911000.2423@shell2.speakeasy.net>

Trent Piepho wrote:
> On Wed, 27 Aug 2008, Daniel [iso-8859-1] Gl�ckner wrote:
>> On Mon, Aug 25, 2008 at 08:40:51PM -0400, Andy Walls wrote:
>>> On Mon, 2008-08-25 at 14:45 +0200, Jean Delvare wrote:

<snipped>

>> The driver fills buffers with instructions for the DMA engine, one buffer
>> for the top field and one for the bottom field. These instructions tell
>> the engine where to write a specific pixel. For interlaced video the
>> instructions for the top field write to line 0, 2, 4, ... in memory and for
>> the bottom field to line 1, 3, 5, ... .
> 
> Keep in mind that _either_ field can be transmitted first.  I.e., in some
> cases one first writes lines 1,3,5 then lines 0,2,4.  I'm not sure if bttv
> supports both field dominances or not, but I think it does.

My particular board always returns top field first on capture.  I don't 
know if that helps.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-08-27  3:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200808251445.22005.jdelvare@suse.de>
2008-08-26  0:40 ` [v4l-dvb-maintainer] bttv driver questions Andy Walls
2008-08-26 23:29   ` Daniel Glöckner
2008-08-27  2:20     ` Trent Piepho
2008-08-27  2:59       ` Robert William Fuller [this message]
2008-08-28 19:43         ` Trent Piepho
2008-08-27  3:45       ` Andy Walls
2008-08-28 19:48         ` Trent Piepho
     [not found]     ` <200808281611.38241.jdelvare@suse.de>
2008-08-28 20:20       ` Daniel Glöckner
2008-08-28 21:42         ` hermann pitton
     [not found]         ` <200808301201.47561.jdelvare@suse.de>
2008-08-30 15:12           ` Daniel Glöckner
2008-08-31 16:37             ` Andy Walls
     [not found]             ` <200809011144.54233.jdelvare@suse.de>
2008-09-01 12:35               ` Daniel Glöckner
     [not found]                 ` <200809012126.06532.jdelvare@suse.de>
2008-09-01 22:54                   ` Daniel Glöckner
     [not found]                     ` <200809021109.31007.jdelvare@suse.de>
     [not found]                       ` <200809021305.12318.jdelvare@suse.de>
2008-09-03 22:29                         ` Daniel Glöckner
     [not found]                           ` <200809051436.18549.jdelvare@suse.de>
2008-09-05 15:51                             ` Daniel Glöckner
2008-09-05 19:16                       ` [v4l-dvb-maintainer] " Trent Piepho
     [not found]   ` <200808281658.28151.jdelvare@suse.de>
2008-08-29 12:09     ` Andy Walls
2008-08-29 22:23       ` Trent Piepho
2008-08-30  0:10         ` Daniel Glöckner
     [not found]           ` <200808300954.19361.jdelvare@suse.de>
2008-08-30 16:44             ` Daniel Glöckner

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=48B4C328.2040502@gmail.com \
    --to=hydrologiccycle@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@redhat.com \
    --cc=xyzzy@speakeasy.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 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.