Hi,
Intresting. Can you try to trim down the register range? I suggest to start with 0x140-0x17f (which are the audio ctrl registers).
I have tried this and came to some interesting conclusions. I could not try this on real 'no sound problem', because I haven't had it for some days now. However, I found a situation that can be tested, on any saa7134 card, I hope. Do this: while the driver is working (I also have xawtv on to see the results immediatelly) poke the whole address range 0x140-0x17f with the value of 0x7f. This makes the sound dissapear, but that is not important. Then unload the saa7134 driver! After reloading the driver again and starting xawtv I get very noisy sound. So, I think this is a situation that must not have happened - after driver reloading the card should always start working in exactly the same way no matter which state it was in before. The remedy is poking two addresses 0x169 and 0x14c with zero (I found this particular addresses using bisection)! I am not sure why this helps because I am not familiar with the card details. In file saa7134-reg.h I see that these registers are SAA7134_AGC_GAIN_SELECT and SAA7134_I2S_OUTPUT_SELECT. I am almost sure that this will not save the 'no sound' problem because I do not see the connection of these two registers with audio carrier sound decoding. It is, however, clear that the card is not entirely initialized. Doesn't this card have a possibility of making total reset, so that after it the card would end up in a known, always the same state? Regards, Stane.
