mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hermann pitton <hermann-pitton@arcor.de>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Steve Castellotti <sc@eyemagnet.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: USB devices supporting raw or sliced VBI for closed captioning?
Date: Mon, 03 Aug 2009 02:02:10 +0200	[thread overview]
Message-ID: <1249257730.3451.53.camel@pc07.localdom.local> (raw)
In-Reply-To: <d9def9db0908020124i26e2a6f2r972a98ae7b8bbe85@mail.gmail.com>


Am Sonntag, den 02.08.2009, 10:24 +0200 schrieb Markus Rechberger:
> On Sun, Aug 2, 2009 at 2:49 AM, hermann pitton<hermann-pitton@arcor.de> wrote:
> >
> > Am Samstag, den 01.08.2009, 03:45 +0200 schrieb Markus Rechberger:
> >> Hi,
> >>
> >> On Sat, Aug 1, 2009 at 1:20 AM, Steve Castellotti<sc@eyemagnet.com> wrote:
> >> >
> >> >        I was wondering if anyone could please point me at a list or similar
> >> > resource for USB capture devices which support raw (or sliced) VBI
> >> > access for producing a closed caption transcript through software such
> >> > as zbvi-ntsc-cc or ccextractor? Specifically I'm wanting a device
> >> > capable of S-Video, Composite, or even Component input, not just ATSC,
> >> > as most USB devices seem focused around these days.
> >> >
> >> >        I've managed to get this working with various ivtv and saa713x based
> >> > PCI devices, but aren't aware of any USB implementations of chipsets
> >> > which use those drivers.
> >> >
> >> >
> >> >        Searching online, I found this archived message:
> >> >
> >> > http://lists.zerezo.com/video4linux/msg16402.html
> >> >
> >> > which states:
> >> >
> >> >> some em2840 and newer devices are able to capture raw vbi in
> >> >> linux (sliced vbi isn't possible yet)
> >> >> em2820, em2800, em2750 do not support vbi at all.
> >> >
> >> >
> >> >        Checking the em28xx driver homepage for recent models, I found this
> >> > entry:
> >> >
> >> > http://mcentral.de/wiki/index.php5/Em2880
> >> >
> >> >> officially the em2880 is em2840 + DVB_T
> >> >
> >> >
> >> >        which implies that not only is the "em2880" series a "newer" device,
> >> > but it should in fact already contain the "em2840" chip specifically
> >> > mentioned.
> >> >
> >> >
> >> >        Later on that same page, in the list of devices:
> >> >
> >> > ATI/AMD TV Wonder 600
> >> >
> >> >
> >> >        and on the manufacturer's page:
> >> >
> >> > http://ati.amd.com/products/tvwonder600/usb/index.html
> >> >
> >> >
> >> >        Under the list of "Input Connectors":
> >> >
> >> >> S-video input with adapter
> >> >
> >> >
> >> >
> >> >        Picking up one of these devices, I attempted to tune into the S-Video
> >> > feed and check the /dev/vbi0 device, but received the same error message
> >> > as I do with all other em28xx devices encountered thus far:
> >> >
> >> >> Cannot capture vbi data with v4l interface:
> >> >> /dev/vbi0 (AMD ATI TV Wonder HD 600) is not a raw vbi device.
> >> >
> >> >
> >> >
> >> >        Can anyone please point me in the right direction?
> >> >
> >> >        I would much prefer to be certain the next purchase is supported.
> >> >
> >> >
> >> >
> >> > Thanks!
> >> >
> >>
> >> we do support Raw VBI for our devices, Sundtek MediaTV Pro for closed
> >> captioning.
> >> Alternatively we also have full support for ATSC-analogTV USB devices
> >> for the US market ([em288x]-[AVFB4910]-[Trident drx-J]-[tda18271]) the
> >> european product which we are selling is also capable of decoding NTSC
> >> closed caption.
> >>
> >> http://sundtek.de/shop/Digital-TV-Sticks-oxid/Sundtek-MediaTV-Pro.html
> >> (this is just the information about the
> >> European/DVB-T/DVB-C/analogTV(raw VBI) device, we do not have the
> >> US/ATSC/analogTV(rawVBI) product listed there, although we do offer it
> >> to business customers) We support it from Linux 2.6.15 on.
> >>
> >> Best Regards,
> >> Markus Rechberger
> >
> > Hi,
> >
> > anything new about how to deal with commercial advertising on lists,
> > depending totally on our source?
> >
> > Please have a look.
> 
> The question was about a device, and I doubt that you can get a device
> for free anywhere. If so there shouldn't be any other company names in drivers,
> or named on the mailinglist (to be fair) which do not support Linux.
> 
> Best Regards,
> Markus

Markus,

that is of course not the question at all.

All questions are about your above sundtek.de link, especially about
what you announce in the user support forum for now.

Given, that Conexant did provide a GPLed driver for cx231xx USB devices
recently, you are intentionally going into the other direction.

I don't even claim, that you should point to this driver too, if it goes
about vbi and closed caption support on USB devices, it has it,

BUT you have gone closed source with your driver, deliver the linux
driver to your customers only, if they are identified by the serial
number of the device you did sell them.

I expect the worst for all further usage conditions.

So, you do not only hide the vbi support you have on em28xx devices now
to us, but likely made it even hard to "hack" such devices
intentionally.

In the same row is, that you announce advanced "direct" audio support
with "tvtime" and soon more features with other GNU/Linux applications
exclusively on your hardware and drivers and don't give back to all
working on them over years.

That is exactly what nobody wants and an abuse of all other
contributors.

Since you do all this intentionally, my vote is clear.

Cheers,
Hermann







      reply	other threads:[~2009-08-03  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1249082438.18313.30.camel@odyssey.sc.user.nz.vpn>
     [not found] ` <d9def9db0907311845r259b129em3bd89b7915718cd5@mail.gmail.com>
2009-08-02  0:49   ` hermann pitton
2009-08-02  8:24     ` Markus Rechberger
2009-08-03  0:02       ` hermann pitton [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=1249257730.3451.53.camel@pc07.localdom.local \
    --to=hermann-pitton@arcor.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mrechberger@gmail.com \
    --cc=sc@eyemagnet.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®