Hi Marcin,
> I did some experiments and it turns out you can make this card
working
> under Linux.
Great! I hope there is still somebody who merges this into the
kernel...
>
> Appropriate entry looks like this:
>
> [SAA7134_BOARD_AVERMEDIA_CARDBUS_PLUS] = {
> .name = "AVerMedia Cardbus TV/Radio Plus",
> .audio_clock = 0x187de7,
> .tuner_type = TUNER_ALPS_TSBE5_PAL,
> .tda9887_conf = TDA9887_PRESENT,
> .inputs = {{
> .name = name_tv,
> .vmux = 1,
> .amux = LINE2,
> .tv = 1,
> },{
> .name = name_comp1,
> .vmux = 3,
> .amux = LINE2,
> },{
> .name = name_svideo,
> .vmux = 8,
> .amux = LINE2,
> }},
> .radio = {
> .name = name_radio,
> .amux = LINE1,
> },
> },
>
> and
>
> /* AVerMedia CardBus Plus */
> .vendor = PCI_VENDOR_ID_PHILIPS,
> .device = PCI_DEVICE_ID_PHILIPS_SAA7134,
> .subvendor = 0x1461, /* Avermedia Technologies Inc */
> .subdevice = 0xb7e9,
> .driver_data = SAA7134_BOARD_AVERMEDIA_CARDBUS_PLUS,
>
>
> (audio_clock is copied from SAA7134_BOARD_CINERGY400_CARDBUS, works
by
> chance, but sound quality is OK - if anybody is brave enough to
open her
> card and check the real value - please give me a shout).
No need to do that. There are only two possible values, and if this
one gives
you sound, it is the correct one.
>
> 5. The card refuses to work when it is inserted during bootup - I
have to
> boot with card unplugged and plug it later. Is this known saa7134
fault or
> maybe some weird interaction with PCMCIA/hotplug/cardmgr/whatever
(I'm
> using custom 2.6.11 on Debian unstable)
I have a similar problem with my Terratec Cinergy 400TV mobile. Don't
know how
to address this issue yet. It might have something to do with
tuner/TDA9887
initialization, as the SAA7134 itself seems to work after
boot/plugin.
Hans
--
Unsubscribe
mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list