public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: V4L: Experimental Sliced VBI API support
Date: Sat, 10 Sep 2005 23:17:11 -0300	[thread overview]
Message-ID: <1126405031.6807.53.camel@localhost> (raw)
In-Reply-To: <20050910184419.53267837.akpm@osdl.org>

Em Sáb, 2005-09-10 às 18:44 -0700, Andrew Morton escreveu:
> Mauro Carvalho Chehab <mchehab@brturbo.com.br> wrote:
> >
> > - adds all defines, ioctls and structs needed for the sliced VBI API
> >
> 
> What is "sliced VBI"?
	Sorry for this... it is too much video jargon :-)
	VBI = Vertical Blank Interval.
	It is related with the way TV signals does work. It sends a line, then,
it has a retrace time to allow the tube to move electrons to the
beginning of the next line. This was the main reason at the beginning of
analog B&W TV.
	There are a lot of bandwidth lost on VBI. So, lots of TV systems uses
it to send other informations, like Closed Capture and Teletext. Also,
broadcasters uses this as a channel to exchange information from the
content producer to their subsidiaries at each city.
	There's already a raw VBI interface on V4L2 api, used for Closed
Captions and Teletext. The decoding is doing at userlevel space and it
is mostly for analog TV signals, non encoded.
	Encoded signals (MPEG, for example), may need also to transmit other
informations (like, for example, display aspect, i.e. 4x3,
widescreen...). Sliced VBI interface is a method to allow the video
stream to transmit this kind of information.
> 
Cheers, 
Mauro.



      reply	other threads:[~2005-09-11  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11  1:14 V4L: Experimental Sliced VBI API support Mauro Carvalho Chehab
2005-09-11  1:44 ` Andrew Morton
2005-09-11  2:17   ` Mauro Carvalho Chehab [this message]

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=1126405031.6807.53.camel@localhost \
    --to=mchehab@brturbo.com.br \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox