By Date:	<-- -->
By Thread:	<-- -->

bttv 2.6.16: wrong VBI_OFFSET?

From: Trent Piepho <xyzzy (at) speakeasy.org>
Date: Mon, 8 May 2006 10:33:01 -0700 (PDT)

On Mon, 8 May 2006, Edgar Toernig wrote:
> Bug reports for AleVT start trickling in.  Is there any
> objection to send a patch to stable (at) kernel.org to revert
> VBI_OFFSET for 2.6.16.15?

Is there anyone with a bt878 and NTSC that can test for the correct NTSC value?
I can provide a program that makes it very easy.  For the cx2388X, the NTSC
value appears to be 220.

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

Follow-Ups:
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Daniel Glöckner <daniel-gl (at) gmx.net>

References:
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Edgar Toernig <froese (at) gmx.de>
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Trent Piepho <xyzzy (at) speakeasy.org>
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Edgar Toernig <froese (at) gmx.de>
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Daniel Glöckner <daniel-gl (at) gmx.net>
- bttv 2.6.16: wrong VBI_OFFSET?
  - From: Edgar Toernig <froese (at) gmx.de>

Prev by Date: Log flood: "scheduling while atomic" (2.6.15.x, 2.6.16.x) - backtrace captured
Next by Date: Add saa6588/RDS support for saa7134
Previous by thread: bttv 2.6.16: wrong VBI_OFFSET?
Next by thread: bttv 2.6.16: wrong VBI_OFFSET?
Index(es):
- Main
- Thread