ras2 wrote:
It's been mentioned here before; if you reboot (or boot Windows and
then boot to Linux), bttv usually doesn't find the tuner
....
Try attached patch and report if the warmboot problem is fixed or not ?
It looks like it. I just tried three warm boots and it found the tuner
every time (this is with bttv.o from 0.9.4, but that probably doesn't
matter).
Fine.
It also got rather lively all of a sudden:
That's because debug=1 tda9887 is set unconditionally in the test patch.
[boot]
Jan 29 01:06:08 vampire kernel: tda9887: probing bt848 #0 i2c adapter
[id=0x10005]
Jan 29 01:06:08 vampire kernel: tda9887: chip found @ 0x86
Jan 29 01:06:08 vampire kernel: bttv0: i2c attach [client=tda9887,ok]
Jan 29 01:06:08 vampire kernel: tda9887_miro: switch on mt2032 tuner via OP2.
Jan 29 01:06:08 vampire kernel: tda9885/6/7: 0xd0 0x6e 0x09 [pinnacle_id=1]
...
Jan 29 01:16:42 vampire last message repeated 12 times
[etc.]
Probably Windows switches off MT2032 (which gets hot)
Surprisingly so (I actually wondered if I would have to install a case
fan because of it, but it doesn't seem so, so far).
and Linux only enables it when it starts tuning.
But then it's too late!
Does that mean that it's turned on all the time now?
Yes.
Gerd, what do you think about switching tuner on/off on open()/close() ?
Other tuners have power saving modes, too: e.g. Philips FM1216:
"tuner can be switched to power-down mode. In this mode the tuner
reduces the current consumption by up to 100 mA."
-
Gunther
