From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Robert Longbottom <rongblor@googlemail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Conexant PCI-8604PW 4 channel BNC Video capture card (bttv)
Date: Tue, 28 Jan 2014 03:02:42 +0100 [thread overview]
Message-ID: <20140128020242.GA31019@minime.bse> (raw)
In-Reply-To: <52E6C7A4.8050708@googlemail.com>
On Mon, Jan 27, 2014 at 08:55:00PM +0000, Robert Longbottom wrote:
> >As for the CPLD, there is not much we can do. I count 23 GPIOs going
> >to that chip. And we don't know if some of these are outputs of the
> >CPLD, making it a bit risky to just randomly drive values on those
> >pins.
>
> Is that because it might do some damage to the card, or to the host
> computer, or both?
If there is damage, it will most likely be restricted to the card.
> Or is it just too hard to make random guesses at
> what it should be doing?
When we cycle through all combinations in one minute, there are about
a hundred PCI cycles per combination left for the chip to be granted
access to the bus. I expect most of the pins to provide a priority
or weighting value for each BT878A, so there should be many combinations
that do something.
> >If we had the original software, we could analyze what it is doing.
> >There is someone on ebay.com selling two of those cards and a cd
> >labled "Rescue Disk Version 1.14 for Linux DVR".
>
> Ah yes, I've just found that, it seems a little pricey!
Maybe the seller is nice person and provides the contents of the CD for
free.
> There is
> also a listing for an "Avermedia 4 Eyes Pro Capture Card PCI 8604"
> which looks pretty much the same, but it doesn't have any software
> with it and searching around for any more information on that hasn't
> got me anywhere.
It's the same card but it is not the Avermedia 4 Eyes Pro.
Daniel
next prev parent reply other threads:[~2014-01-28 2:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:39 Conexant PCI-8604PW 4 channel BNC Video capture card (bttv) Robert Longbottom
2014-01-20 22:55 ` Andy Walls
2014-01-21 9:27 ` Robert Longbottom
2014-01-21 10:19 ` Daniel Glöckner
2014-01-21 19:49 ` Robert Longbottom
2014-01-21 20:59 ` Robert Longbottom
2014-01-22 11:53 ` Daniel Glöckner
2014-01-22 13:09 ` Robert Longbottom
2014-01-22 13:50 ` Daniel Glöckner
2014-01-22 18:15 ` Robert Longbottom
2014-01-23 13:27 ` Daniel Glöckner
2014-01-23 14:29 ` Robert Longbottom
2014-01-25 15:23 ` Daniel Glöckner
2014-01-26 11:21 ` Robert Longbottom
2014-01-26 12:55 ` Daniel Glöckner
2014-01-26 16:23 ` Robert Longbottom
2014-01-27 3:20 ` Daniel Glöckner
2014-01-27 20:55 ` Robert Longbottom
2014-01-28 2:02 ` Daniel Glöckner [this message]
2014-02-05 13:16 ` Robert Longbottom
2014-02-11 13:38 ` Daniel Glöckner
2014-02-11 18:25 ` Robert Longbottom
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=20140128020242.GA31019@minime.bse \
--to=daniel-gl@gmx.net \
--cc=linux-media@vger.kernel.org \
--cc=rongblor@googlemail.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