public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Cookson <it@sca-uk.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	stoth@kernellabs.com
Subject: Re: Canvassing for Linux support for Startech PEXHDCAP
Date: Tue, 17 Sep 2013 12:15:23 -0300	[thread overview]
Message-ID: <5238720B.7040106@sca-uk.com> (raw)
In-Reply-To: <CAGoCfiwVPGKSYOObirz+X3_AN6S1LL5Eff9kcWswcHx-msguiA@mail.gmail.com>

On 16/09/2013 19:09, Devin Heitmueller wrote:
 > To be clear, this card is a *raw* capture card.  It does not have any
 > hardware compression for H.264.  It's done entirely in software.

Ok, well I misunderstood that.  And, in addition, I also thought that 
hardware encoding *reduced* latency, something you seem to indicate is 
not true.

If this is stored in a file, somehow it needs to be encoded, I just 
imagined that metal was faster than code.

 > Aside from the Mstar video decoder (for which there is no public
 > documentation), you would also need a driver for the saa7160 chip,
 > which there have been various half-baked drivers floating around but
 > nothing upstream, and none of them currently support HD capture
 > (AFAIK).

Well the chip thing is confusing me.

1) I don't understand the difference between the MST3367CMK-LF-170 and 
the saa7160.  Is one analogue and one digital?  Or do they perform 
different steps in the process (like one does encoding and one does the 
DMA thing?

2) If you look here,

http://katocctv.en.alibaba.com/product/594834688-213880911/1080p_PCIe_Video_Grabber_Video_Capture_Card.html

You'll see a very similar card with an extra chip.  You can just see 
that it is produced by Gennum (but I can't see the number).  There is 
also another chip on the underside, maybe this is the saa7160? And maybe 
it's on the underside of the PEXHDCAP too.  This is actually the one I 
saw working.  As I say it was very fast and high quality, but under windows.

Scroll down and you see this:

     Operation System: WINDOWS XP /VISTA/ 7 Linux 2.6. 14 or higher 
(32-bit and 64-bit)

Drilling into this, it appeared the statement was more aspirational than 
actual, but that it *had* been compatible, but there was not yet an 
available driver.  They would need to recompile something to include the 
latest linux libraries before it would be possible to write the 
drivers.  I've no idea what this could mean.  Although 2 clients had 
indeed written gstreamer drivers, one was Cisco systems, but had kept 
the code to themselves.

 > and none of them currently support HD capture (AFAIK).

What does this mean?  No saa7160 drivers, or no drivers period?  I have 
the Intensity Pro doing full-screen 1080i capture with minimal latency, 
but I hate the decklinksrc module.  It just does nearly nothing.  Maybe 
it could be re-written for v4l2src, but anyway it only accepts YPbPr, as 
I said before.

 > As always, a driver *can* be written, but it would be a rather large
 > project (probably several weeks of an engineer working full time on
 > it, assuming the engineer has experience in this area).  In this case
 > it's worse because a significant amount of reverse engineering would
 > be required.

Kato Vision agreed with you.  They were saying a few months (maybe two 
or three).  They didn't offer to write it, but they offered technical 
support with the driver-writing.

Thanks for your input.

Regards

Steve

  reply	other threads:[~2013-09-17 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 20:27 Canvassing for Linux support for Startech PEXHDCAP Steve Cookson
2013-09-16 22:09 ` Devin Heitmueller
2013-09-17 15:15   ` Steve Cookson [this message]
2013-09-17 15:38     ` Devin Heitmueller
2013-09-17 17:55       ` Steve Cookson

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=5238720B.7040106@sca-uk.com \
    --to=it@sca-uk.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.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