On Wednesday 18 July 2007 11:27:36 am Michael T. Dean wrote:
> On 07/18/2007 05:42 AM, Matthew Wire wrote:
> > Following on from the mail about Xbox hardware which I will be attempting
> > to make a detection patch for, I'd also like to detect the presence of a
> > pvr-350 card since there are a number of settings specific to this card.
> >
> > Browsing the web suggests that lspci -v should always contain the
> > following strings when the pvr-350 is present:
> > Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2
> > Encoder (rev 01)
> > Subsystem: Hauppauge computer works Inc. WinTV PVR-350
>
> As a former user of a PVR-350, I'm pretty sure there's more to it than
> that (i.e. the string is not always so nicely specific). I highly
> recommend asking on the appropriate ivtv list as they've already done
> the work of determining how to autodetect the card type...
Yeah, the bits in lspci output are entirely dependent on the pci ids being
properly mapped for the specific pci ids for your card, so some newer cards,
especially with older pci id data, may not show up exactly like that.
Excerpt from /usr/share/hwdata/pci.ids on my system:
0070 Hauppauge computer works Inc.
0003 WinTV PVR-250
0009 WinTV PVR-150
0801 WinTV PVR-150
0807 WinTV PVR-150
4000 WinTV PVR-350
4001 WinTV PVR-250 (v1)
4009 WinTV PVR-250
4800 WinTV PVR-350
4801 WinTV PVR-250 MCE
4803 WinTV PVR-250
8003 WinTV PVR-150
8801 WinTV PVR-150
c801 WinTV PVR-150
e807 WinTV PVR-500 MCE (1st tuner)
e817 WinTV PVR-500 MCE (2nd tuner)
So if your PVR-350 didn't have a subsystem PCI ID of 0070:4000 or 0070:4800,
it wouldn't get properly labeled in lspci output on my system. If it wasn't
already obvious, the 0070 portion is the vendor PCI ID, the second part is
the device-specific ID. Its also possible to pull the latest-n-greatest pci
id file straight from sourceforge too, btw, though the two above appear to be
all that's in the latest-n-greatest too.
http://pciids.sourceforge.net/
--
Jarod Wilson
jarod at wilsonet.com