Philip Rowlands <[EMAIL PROTECTED]>, Wed, 24 Aug 2005 13:18:23 +0100 (BST) > All those hauppauge_tuner[] tuners are handled as > TUNER_PHILIPS_FM1216ME_MK3. I assert that the byteswap code above is > called for my tuner (I added some debugging printk lines). Well, I read the datasheet a little bit to fast and assumed the P-table was started with MSB but it's actually starting with bit-0, ie from my log the FQ1216AME MK4 does look as it has the same interface as the FQ1216ME MK3.
> The weirdest effect of that code, to my mind, is the non-idempotent > tuning control. If I tune to the same frequency twice sequentially, I > can get different code paths, different i2c bytes sent, but it still > works. What's going on? Why is variable byte order a useful feature? It could have something to do with the different "pumps" in AGC and AFC... > I don't think I want external (to the tuner) AGC in. What fixed my sound > was to get the tda988x to output its AGC on OP2 (bit B7). Right now I > don't want to touch the AB register, as I've no idea what a Takeover > Point is or does. Well do you mean that you set B7 to 1 or 0 (1=deactivate/highstate). Please post exactly all the bits and bytes you change. > Also, the way tuner.c is written, you'll never write to AB, as CB is > hard-coded in the tuners array. I agree... (it's set to A=2 at POR) > >Start with control registers if new frequence is lower or same as > >current (ie not only when less). > I don't see why this would be either necessary or desirable. I, however, > do not design signal processing circuitry :) Se one of the above responses. > Are those sequential or just cut-n-paste examples? What's the observed > behaviour when going (up, same) and (down, same)? Sequential from LiveTV, stop, LiveTV, change channel, change channel (up all the time as the PLL value informs). /Corax
