From: CityK <cityk@rogers.com>
To: Chris Wilson <info@coolcatpc.com>,
Linux-media <linux-media@vger.kernel.org>
Subject: Re: [Bulk] RE: New Card - BT878
Date: Mon, 16 Feb 2009 13:18:30 -0500 [thread overview]
Message-ID: <4999ADF6.4070604@rogers.com> (raw)
In-Reply-To: <001f01c98fea$2823e4d0$786bae70$@com>
Chris Wilson wrote:
> Howdy, thanks for all the info! :) its greatly appreciated. Thanks for all
> the background information as well.
>
>
> This is the output from lspci -s 01:05.0 -vnn for my BT878 Card:
>
> 01:05.0 0400: 109e:036c (rev 11)
> Flags: medium devsel, IRQ 10
> Memory at fd800000 (32-bit, prefetchable) [disabled] [size=4K]
> Capabilities: [44] Vital Product Data
> Capabilities: [4c] Power Management version 0
>
> I've had this card working before, the ol' noggin does'nt want to fire on
> all eight and remind me how I did it ;).
>
> Thanks a bunch once again!
Hi Chris,
Please don't drop the mailing lists from the discussion (use your email
client's "reply all" feature) ... I have cc'ed the Linux-media list back
in. Also, in future, please don't top post.
Regarding this card, the absence of a device subsystem ID in your output
for the above command leads me to think that your card likely lacks an
EEPROM. Do you know the name of the device or is it just a generic bttv
card? (i was hoping we could have ascertained its identity from the
above command, but obviously no luck on that route).
Given that you've been able to run it under Linux before (as per your
above and previous message's statements), that is certainly encouraging.
Can you please provide the output from dmesg.
prev parent reply other threads:[~2009-02-16 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 0:25 New Card - BT878 Chris S. Wilson
2009-02-15 22:19 ` CityK
[not found] ` <001f01c98fea$2823e4d0$786bae70$@com>
2009-02-16 18:18 ` CityK [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=4999ADF6.4070604@rogers.com \
--to=cityk@rogers.com \
--cc=info@coolcatpc.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