From: Richard F <lists@keynet-technology.com>
To: linux-media@vger.kernel.org
Subject: unrecognised BT878 video capture card
Date: Sat, 30 Jun 2012 14:56:58 +0100 [thread overview]
Message-ID: <4FEF05AA.70209@keynet-technology.com> (raw)
This is an IVC-100-LEG from ebay
http://www.ebay.co.uk/itm/370609954186?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
It works with insmod option card=110 which is for the vanilla IVC-100
[ 8.257854] Linux video capture interface: v2.00
[ 8.264465] bttv: driver version 0.9.18 loaded
[ 8.265765] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 8.267108] bttv: Bt8xx card found (0).
[ 8.268435] bttv 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 8.269833] bttv0: Bt878 (rev 17) at 0000:04:00.0, irq: 18, latency:
32, mmio: 0xd0001000
[ 8.271381] bttv0: subsystem: ff03:a132 (UNKNOWN)
[ 8.272753] please mail id, board name and the correct card= insmod
option to linux-media@vger.kernel.org
[ 8.272756] bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]
[ 8.274227] bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
[ 8.274307] bt878 #0 [sw]: Test OK
Output of lspci -vv
04:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
Subsystem: Device ff03:a132
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (4000ns min, 10000ns max)
Interrupt: pin A routed to IRQ 18
Region 0: Memory at d0001000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data <?>
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: bttv
Kernel modules: bttv
04:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
Subsystem: Device ff03:a132
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (1000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data <?>
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
reply other threads:[~2012-06-30 13:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FEF05AA.70209@keynet-technology.com \
--to=lists@keynet-technology.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).