pinnacle 310i Problems maybe i2c

[Hartmut Hackmann <hartmut.hackmann (at) t-online.de>]

Hi,

KevinLuX wrote:
> hermann pitton wrote:
>
> > Am Freitag, den 10.02.2006, 17:59 +0100 schrieb KevinLuX:
> >  
> >
> > > > [....] That's why I
> > > > asked for a _cold_ reboot and then try with card=77 and mercurial.
> > > >
> > > >
> > > >     
> > >
> > > you mean a _cold_ boot non reboot....if i reboot in each case is hot 
> > > boot -_-
> > > true??
> > >   
> >
> >
> > Yes, cold boot is better.
> >
> > You had 2.4.14 and if you tried something with tuner=54/tda8290 the
> > tda8275a goes gaga upon wrong initialization sequence and also other i2c
> > devices are affected.
> >
> > To get it back needs to have the machine not connected to any power for
> > some seconds. If it still works in m$ it is something else.
> > You might try another PCI slot then. Also an instable PSU has caused
> > similar troubles already.
> >
> > Hermann
> >
> >
> > --
> > video4linux-list mailing list
> > Unsubscribe 
> > mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/video4linux-list
> >  
> OOoooohhhh yeahhhhhh!!!
> Goodd Herman, everythink works now in ANALOG mode!! Thanks a LOT!!!
> i write here some tips to other user that could have my problem
> So... Pinnacle 310i is very different from 300i here thereis an image :
> http://www.karondimonio.it/310i.png
> According to Hermann : [tda8290 is the IF part of the 8275a silicon 
> tuner on your board
> integrated in the saa7131e chip. No tuning this way. The current code is 
> even assumed
> to be able to detect the difference between a tda9887 and tda8290, also 
> between the
> older 8275 and the hybrid 8275a silicon tuner, which should result in a 
> tuner line in
> "dmesg" with tda8290/75a registered. No chance without it!]
Well, that's only partly correct. The tda9887 driver is not able to detect
that it acts with the wrong chip. But if you load the tuner module first,
this one finds out whether the IF chip is a tda8290 or not. The recent
version also finds out whether the tuner is a 8275 or the a-version.
This does *not yet* hold for the dvb module. Setting the wrong card type
here might cause the attempt to initialize the 8275a as the non a version.
This turns the crystal oscillator off and so there is no longer a clock for
tda8290 and tda10046. The only way out of this is a power cycle.

Best regards
   Hartmut

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