public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Curtis Hall <curt@bluecherry.net>
To: linux-media@vger.kernel.org
Subject: Re: [bttv] Auto detection for Provideo PV- series capture cards
Date: Fri, 26 Feb 2010 16:06:41 -0600	[thread overview]
Message-ID: <4B8845F1.5070608@bluecherry.net> (raw)
In-Reply-To: <4B884034.8080508@redhat.com>

Mauro Carvalho Chehab wrote:
> Let's go by parts:
>
> The entry for PV-150 were added at -hg tree by this changeset:
> changeset:   784:3c31d7e0b4bc
> user:        Gerd Knorr
> date:        Sun Feb 22 01:59:34 2004 +0000
> summary:     Initial revision
>
> Probably, this is a discontinued model, but I don't know for sure.
>   
We have been Provideo's US distributor since late 2004 and I've not 
heard of a PV-150 part number, and isn't not a current part number.
> This one is easy:
>   
> [   13.438412] bttv0: subsystem: 1830:1540 (UNKNOWN)
>
> As this PCI ID is not known, it is just a matter of associating the PV-183
> ID's with card 98.
>   

I figured, thanks
> Just for reference the PV-149 / PV-981 / PV-183 series cards are:
>
> PV-149 - 4 port, 4 BT878a chips - no forced card setting required
> PV-155 - 16 port, 4 BT878a chips - card=77,77,77,77  (Shares the same
> board and PCI ID / subsystem as the PV-149)
>   
>
> Hmm... PV-155 shares the same PCI ID as PV-149, but require a different
> entry, then we shouldn't add it to the PV-150 autodetection code.
>   
Okay.  You can easily access four ports on the PV-155 / PV-981, but to 
access the sub (/dev/videoX,1-3) channels you need to add the modprobe line.
> The better would be to check with the manufacturer if is there a
> way to detect between those two boards (maybe reading eeprom?).
>
>   
I can find out, but getting technical data from Provideo can be more 
painful then pulling teeth.
> Why do you need the card= parameter, if it shares the same subsystem 
> ID as the other PV-981 models?

I think I explained that about with the sub channels, if I'm missing 
something let me know.

Thanks!

-- 
--
Curtis Hall (curt@bluecherry.net)
Bluecherry - www.bluecherry.net
(877) 418-3391 x 201 


  reply	other threads:[~2010-02-26 22:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 20:25 [bttv] Auto detection for Provideo PV- series capture cards Curtis Hall
2010-02-26 20:43 ` Devin Heitmueller
2010-02-26 20:48   ` Curtis Hall
2010-02-26 20:57     ` Devin Heitmueller
2010-02-26 21:42 ` Mauro Carvalho Chehab
2010-02-26 22:06   ` Curtis Hall [this message]
2010-02-27  2:08     ` Mauro Carvalho Chehab

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=4B8845F1.5070608@bluecherry.net \
    --to=curt@bluecherry.net \
    --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