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: Wed, 22 Jan 2014 12:53:34 +0100 [thread overview]
Message-ID: <20140122115334.GA14710@minime.bse> (raw)
In-Reply-To: <52DEDFCB.6010802@googlemail.com>
On Tue, Jan 21, 2014 at 08:59:55PM +0000, Robert Longbottom wrote:
> On 21/01/2014 19:49, Robert Longbottom wrote:
> >Here are some high-res pictures of both sides of the card. Scanned at
> >600dpi (300dpi the tracks were very close). Good idea to scan it by the
> >way, I like that, much better result than with a digital camera.
> >
> >http://www.flickr.com/photos/astrofraggle/12073752546/sizes/l/
> >http://www.flickr.com/photos/astrofraggle/12073651306/sizes/l/
ok:
- The Atmel chip is an AT24C02 EEPROM. Does one of the 878As have a PCI
subsystem ID?
- The 74HCT04 is used to drive the clock from the oscillator to the
878As.
- The 74HCT245 is a bus driver for four pins of the connector CN3.
- The unlabled chip is probably a CPLD/FGPA. It filters the PCI REQ#
lines from the 878As and has access to the GNT# and INT# lines,
as well as to the GPIOs you mentioned. The bypass caps have a layout
that fits to the Lattice ispMACH 4A.
- There is no mux or gate between the BNC connectors and the 878As.
The BNCs are on MUX0. MUX1 is connected to the two unpopulated 2x5
Headers.
So the UNKNOWN/GENERIC card entry should have the BNC connectors on its
first V4L input.
Have you tried passing pll=35,35,35,35 as module parameter?
Daniel
next prev parent reply other threads:[~2014-01-22 11:53 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 [this message]
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
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=20140122115334.GA14710@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