| By Date: | <-- --> |
| By Thread: | <-- --> |
Hi,
Ups, i had a different impression, sorry!Am Samstag, den 11.02.2006, 02:14 +0100 schrieb Hartmut Hackmann:
Hi, Hermann
hermann pitton wrote:
Am Samstag, den 11.02.2006, 01:04 +0100 schrieb Hartmut Hackmann:
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.
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.
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
-- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list