Am Freitag, den 30.06.2006, 10:23 +1000 schrieb Marc Bakker:
> Hi
>
> I now have 2 AverMedia 777 cards, one purchased in March 2006 and one
> in June 2006. The June card has a different PCI ID (!!!!!!!!) and
> consequently doesn't work.
>
> I resolved this by adding it to the saa7134-cards.c code but I'm not
> sure if this is a suitable fix or how to post the change if this is
> the way to go, I really just play around with code but don't write
> it :)
>
> The PCI info of the March card (the working one) is:
>
> 02:02.0 Class 0480: 1131:7134 (rev 01)
> Subsystem: 1461:2c05
> Flags: bus master, medium devsel, latency 64, IRQ 17
> Memory at fcfee400 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [40] Power Management version 1
>
>
> The info for the June card that's not working is:
>
> 02:01.0 Class 0480: 1131:7133 (rev d1)
> Subsystem: 1461:2c05
> Flags: bus master, medium devsel, latency 64, IRQ 22
> Memory at fcfee800 (32-bit, non-prefetchable) [size=2K]
> Capabilities: [40] Power Management version 2
>
Hi Marc,
thanks! If there are no further issues, just add the card and change the
PCI bridge from
> .vendor = PCI_VENDOR_ID_PHILIPS,
> .device = PCI_DEVICE_ID_PHILIPS_SAA7134, /* SAA 7131E */
> .subvendor = 0x1461,
> .subdevice = 0x2c05,
> .driver_data = SAA7134_BOARD_AVERMEDIA_777,
> },{
to PCI_DEVICE_ID_PHILIPS_SAA7133 in saa7134-cards.c.
Must have slipped through. We have no other way to distinguish later than saa7130, saa7134 and saa7133.
Everything newer as saa7133 comes up as saa7133 currently.
Mike, was there ever a saa7134 device?
Look at the TRIO above now.
The saa7131e is not detected as such.
Cheers,
Hermann
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
