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

pinnacle 310i Problems maybe i2c

Am Sonntag, den 12.02.2006, 00:35 +0100 schrieb Hartmut Hackmann:
> Hi,
> 
> hermann pitton wrote:
> > Am Samstag, den 11.02.2006, 02:14 +0100 schrieb Hartmut Hackmann:
[...]
> >>>Hartmut,
> >>>
> >>>well!
> >>>
> >>>I still don't see what I have missed for userland debugging
> >>>without NDAs.
> >>>
> >>
> >>The point is that distinguishing tda9887 and tda8290 only works if the
> >>tuner module is loaded first. If tda9887.ko is initialized first, it will
> >>just claim the address and things are lost.
> > 
> > 
> > Yes, that is obvious.
> > 
> Ups, i had a different impression, sorry!
> > 

No problem. Also any device from tvaudio will take it. The insmod
options are already very flexible, but it should be made bttv specific
and stop ghosting around.

> >>Please correct me if i am wrong here: If the modules are loaded by dependency
> >>and request only, the loading sequence is:
> >>saa7134.ko, tuner.ko and tda9887.ko - perfect from many points of view.
> >>But for some pinnacle cards, we need a different sequence:
> >>saa7134.ko, tda9887.ko, tuner.ko.
> >>With this sequence, distinguishing the IF chips goes wrong. If i remember
> >>things correctly, it will also fail with the FMD1216 tuner.
> >>Do you hear a bomb ticking?
> > 
> > 
> > Yes, I can see it already for the FMD1216ME H-3 hybrid in 50 % of the
> > tries with latest.
> > 
> > Greetings,
> > Hermann
> > 
> Oh, that's bad news!
> I have an idea what to do with the Pinnacle cards. It is somewhat ugly
> but the same trick should work with the FMD1216: Do the important
> intiatlization step in the card init code in saa7134-cards.c, so
> initialise the TDA9887 ports for pinnacle and initialize the PLL chip
> of the FMD1216.
> 
> That means we have chip specific code there (what i don't like) but
> at least it should do the trick.
> 
> Best regards
>     Hartmut
> 
> --

Hartmut, it was late and it is already again and "normal" life
continous ...

What was meant is the autodetection of the different md7134 types and
there is some drift meanwhile. With tuner=38 specified it is still
reliable, but not 100% stable anymore.

Leaving it to full autodetection causes the about 1:2 missing.

Cheers,
Hermann


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