HI Thanks,
But this is confusing for me. Please give a step by step instruction
to do this :
>> Change the vmux of card = 3 in saa7134-cards.c from one to 3
So you want me to change the line " .vmux = 1, <--change to
vmux = 3" in kernel source code and recompile the entire kernel ?
There is no other changes required in source code isn't it ?
I am not sure about what you mean by cold boot. Please give simple
instruction to get that done. I am new o this field, so It is
difficult to understand these stuffs that easily.
On Fri, Jul 24, 2009 at 11:36 AM, hermann pitton<hermann-pitton@xxxxxxxx> wrote:
> Hi,
>
> Am Freitag, den 24.07.2009, 10:48 +0530 schrieb unni krishnan:
>> > Hi Unni,
>> Hi Hermann,
>>
>> >
>> > we have lots of saa7130 cards without eeprom on it providing not at
>> > least a valid PCI subvendor and subdevice, so we can't know what it is
>> > at all, neither for the tuner type and also not for how video and audio
>> > inputs are connected.
>> >
>> > If you can tell a card with working video and another one with working
>> > audio, it should not be hard to get something together for both on TV
>> > from the tuner as a start.
>>
>> The option
>>
>> modprobe saa7134 card=3 tuner=55
>>
>> gives me sound without much noise but no video
>
> You need the external audio mux gpio switching of the FlyVideo2000
> card=3.
>
>> This gives me video, but no audio
>>
>> modprobe saa7134 card=37 tuner=55
>>
>
> But you also need the vmux=3 of card=37 for it.
> Change the vmux of card = 3 in saa7134-cards.c from one to 3 and
> recompile and install and try again with your "maybe" tuner.
>
>
> [SAA7134_BOARD_FLYVIDEO2000] = {
> /* "TC Wan" <tcwan@xxxxxxxxx> */
> .name = "LifeView/Typhoon FlyVIDEO2000",
> .audio_clock = 0x00200000,
> .tuner_type = TUNER_LG_PAL_NEW_TAPC,
> .radio_type = UNSET,
> .tuner_addr = ADDR_UNSET,
> .radio_addr = ADDR_UNSET,
>
> .gpiomask = 0xe000,
> .inputs = {{
> .name = name_tv,
> .vmux = 1, <--change to vmux = 3
> .amux = LINE2,
> .gpio = 0x0000,
> .tv = 1,
> },{
> .name = name_comp1,
> .vmux = 0,
> .amux = LINE2,
> .gpio = 0x4000,
> },{
> .name = name_comp2,
> .vmux = 3,
> .amux = LINE2,
> .gpio = 0x4000,
> },{
> .name = name_svideo,
> .vmux = 8,
> .amux = LINE2,
> .gpio = 0x4000,
> }},
> .radio = {
> .name = name_radio,
> .amux = LINE2,
> .gpio = 0x2000,
> },
> .mute = {
> .name = name_mute,
> .amux = LINE2,
> .gpio = 0x8000,
> },
> },
>
>
>> >
>> > Also, if you do a cold boot without forcing any card, there might be a
>> > slight chance, that the gpio configuration on card init has been seen
>> > previously.
>>
>> Sorry, do you want me to just reboot the system ? I have already
>> rebooted the system many times. Is there any other thing that I need
>> to do before/after reboot ? I am new to Linux devices
>>
>
> If you tried different cards with different gpio configurations
> previously, those settings are not cleared, except you take care for it.
>
> Easiest is to do a cold boot, to see the card coming up untouched on
> gpios.
>
> I did not care yet, if we have it already duplicate, but likely try to
> look it up in the evening here.
>
> Cheers,
> Hermann
>
>
>
--
---------------------
With regards,
Unni
"A candle loses nothing by lighting another candle"
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
