All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, Andrea Venturi <a.venturi@avalpa.com>
Cc: linux-media@vger.kernel.org
Subject: Re: advice on Easycap dongles and VBI interface..
Date: Thu, 5 Dec 2013 09:22:40 -0300	[thread overview]
Message-ID: <20131205122239.GB2345@localhost> (raw)
In-Reply-To: <52A0693C.7060704@xs4all.nl>

Hi Andrea and Hans,

On Thu, Dec 05, 2013 at 12:53:32PM +0100, Hans Verkuil wrote:
> 
> > - finally which approach do you suggest for supporting this ancient
> > feature, if feasibiliy tests are ok: - a libusb quick hack? - an
> > implementation of the bindings between user level /dev/vbi and
> > underlying SAA711x routines?
> 
> The problem is that I don't believe we have any stk1160 documentation.

I do have the stk1160 chip datasheet. However, it's not publicly
available and I'm not sure I should disclose it (although syntek never
advise me against it). In additio, the datasheet is not very verbose
and the information is scarce and often incomplete.

> And I wonder if the device can support VBI at all.
> 

Apparently it does: at least there's a flag to "enable" VBI mode.

> You are better off choosing devices that already have VBI support: the
> em28xx supports it, so do bt8xx, cx18 and ivtv.
> 

I agree with this. I don't have any VBI source so there's no way I can
work on this (not to mention it's not something lots of users need).
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2013-12-05 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 10:43 advice on Easycap dongles and VBI interface Andrea Venturi
2013-12-05 11:53 ` Hans Verkuil
2013-12-05 12:22   ` Ezequiel Garcia [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=20131205122239.GB2345@localhost \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=a.venturi@avalpa.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.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.