By Date: <-- -->
By Thread: <-- -->

bttv msp3400 2.6.15.6 - > 2.6.16 stereo stop working

On Monday 27 March 2006 22:03, Roland Scheidegger wrote:
> Daniel Smolik wrote:
> > If I boot to kernel with development drivers and  only reboot to
> > another where msp3400 works , MSP3400 isn't detected. I must turn
> > off computer and boot again :-(.
>
> Just wanted to say I can confirm that behaviour (not surprising, I
> have exactly the same card (type 11)). I believe the msp3400 chip
> doesn't have its reset pin wired to anything except a capacitor, so
> once you've sent it commands which cause it to lockup or something so
> it no longer responds to i2c commands it will stay dead and cannot be
> revived - it won't get recognized at all again with any version of
> the driver afterwards. So it looks like something is wrong with the
> msp3400 driver in the current tree causing the msp3400 to cease to
> work.
>
> btw somewhat unrelated but what still doesn't work (and never has) is
> audio muting when channels are switched. audio gets unmuted very
> fast, and the msp3400 itself is never muted, which leads to about 3-5
> crackling noises when a channel is switched. It looks like you'd need
> to do it manually, as the chip doesn't really have any ability to
> mute automatically. It has some mute function (ad_cv bit 9), which
> I've tried playing with but it's utterly useless (well it even
> basically says so in the datasheet, so I'm not really surprised) -
> all it does is mute some perfectly good channels, but it does
> absolutely nothing when switching channels.

I'm sorry, I'm getting confused. Now there suddenly are three problems 
with 2.6.16:

1) xawtv thinks channels are mono even though they are stereo.
2) after a reboot the msp3400c fails to work (is this interpreted 
correctly? I'm not sure that I completely understood the problem.)
3) the msp3400c doesn't mute.

1) is caused by waiting not long enough in xawtv to get a reliable 
reading from msp3400, this should be solved in the latest v4l-dvb tree 
(please confirm this!)

2) does this also happen with the latest v4l-dvb? Does this also happen 
with 2.6.15? I don't think I made any changes to the reset code.

3) this apparently never worked. Can you test this again in the latest 
v4l_dvb? If you go to the msp3400c_init_data table and adjust the 
0x00d0 value to 0x0ed0 and try it? I'm interested in hearing the 
results. What TV-audio standard is used where you live?

Thank you for the feedback.

	Hans

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list