<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Oct 10, 2008 at 2:36 AM, hermann pitton <span dir="ltr"><<a href="mailto:hermann-pitton@arcor.de">hermann-pitton@arcor.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
Am Donnerstag, den 09.10.2008, 22:15 +0200 schrieb klaas de waal:<br>
<div><div></div><div class="Wj3C7c">> Hi Jeremy,<br>
><br>
> I have the Technotrend C-1501 now locking at 388MHz.<br>
> The table tda827xa_dvbt contains the settings for each frequency<br>
> segment.<br>
> The frequency values (first column) are for the frequency plus the<br>
> IF, so for 388MHz<br>
> this is 388+5 gives 393 MHz. The table starts a new segment at 390MHz,<br>
> it then<br>
> starts to use VCO2 instead of VCO1.<br>
> I have now (hack, hack) changed the segment start from 390 to 395MHz<br>
> so<br>
> that the 388MHz is still tuned with VCO1, and this works OK!!<br>
> Like this:<br>
><br>
> static const struct tda827xa_data tda827xa_dvbt[] = {<br>
> { .lomax = 56875000, .svco = 3, .spd = 4, .scr = 0, .sbs =<br>
> 0, .gc3 = 1},<br>
> { .lomax = 67250000, .svco = 0, .spd = 3, .scr = 0, .sbs =<br>
> 0, .gc3 = 1},<br>
> { .lomax = 81250000, .svco = 1, .spd = 3, .scr = 0, .sbs =<br>
> 0, .gc3 = 1},<br>
> { .lomax = 97500000, .svco = 2, .spd = 3, .scr = 0, .sbs =<br>
> 0, .gc3 = 1},<br>
> { .lomax = 113750000, .svco = 3, .spd = 3, .scr = 0, .sbs =<br>
> 1, .gc3 = 1},<br>
> { .lomax = 134500000, .svco = 0, .spd = 2, .scr = 0, .sbs =<br>
> 1, .gc3 = 1},<br>
> { .lomax = 154000000, .svco = 1, .spd = 2, .scr = 0, .sbs =<br>
> 1, .gc3 = 1},<br>
> { .lomax = 162500000, .svco = 1, .spd = 2, .scr = 0, .sbs =<br>
> 1, .gc3 = 1},<br>
> { .lomax = 183000000, .svco = 2, .spd = 2, .scr = 0, .sbs =<br>
> 1, .gc3 = 1},<br>
> { .lomax = 195000000, .svco = 2, .spd = 2, .scr = 0, .sbs =<br>
> 2, .gc3 = 1},<br>
> { .lomax = 227500000, .svco = 3, .spd = 2, .scr = 0, .sbs =<br>
> 2, .gc3 = 1},<br>
> { .lomax = 269000000, .svco = 0, .spd = 1, .scr = 0, .sbs =<br>
> 2, .gc3 = 1},<br>
> { .lomax = 290000000, .svco = 1, .spd = 1, .scr = 0, .sbs =<br>
> 2, .gc3 = 1},<br>
> { .lomax = 325000000, .svco = 1, .spd = 1, .scr = 0, .sbs =<br>
> 3, .gc3 = 1},<br>
> #ifdef ORIGINAL // KdW test<br>
> { .lomax = 390000000, .svco = 2, .spd = 1, .scr = 0, .sbs =<br>
> 3, .gc3 = 1},<br>
> #else<br>
> { .lomax = 395000000, .svco = 2, .spd = 1, .scr = 0, .sbs =<br>
> 3, .gc3 = 1},<br>
> #endif<br>
> { .lomax = 455000000, .svco = 3, .spd = 1, .scr = 0, .sbs =<br>
> 3, .gc3 = 1},<br>
> etc etc<br>
><br>
> I plan to do a test on the all frequencies in the near future, at<br>
> least on all the Dutch Ziggo frequencies.<br>
> Because I cannot test what will happen if the driver is used for DVB-T<br>
> (what<br>
> the name of the table suggests) it might be best to make a separate<br>
> tda827xa_dvbc table.<br>
><br>
> About the timeout messages, they come from the SAA7134 and they happen<br>
> fairly random. I have looked at debug traces and everytime it happens<br>
> it<br>
> does a retry and then succeeds, so I think this can be ignored for the<br>
> time being.<br>
> Maybe you can check if the fix/hack also works for you?<br>
> If there is an official maintainer of this driver, maybe he can<br>
> comment?<br>
><br>
> Groetjes,<br>
> Klaas<br>
><br>
<br>
</div></div>just scrolling through mails and did not look it up yet.<br>
<br>
But you likely mean tda8274a DVB-C, tda10023 and saa7146.<br>
<br>
Are we still here?<br>
<a href="http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025634.html" target="_blank">http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025634.html</a><br>
<br>
Please don't top post, you get more readers.<br>
<br>
Cheers,<br>
<font color="#888888">Hermann<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
><br>
> On Tue, Sep 30, 2008 at 11:18 AM, <<a href="mailto:jerremy@wordtgek.nl">jerremy@wordtgek.nl</a>> wrote:<br>
> Hi Klaas,<br>
><br>
> Perhaps its an idea to post this on the linux-dvb mailing<br>
> list, if anything<br>
> it keeps the subject alive.<br>
><br>
> I've spent an hour or so playing with several of the<br>
> parameters of the<br>
> demodulator (the tda10023), mostly because this was suggest in<br>
> one of the<br>
> older posts about this issue. However none of my efforts gave<br>
> any desired<br>
> result and quickly got tired of unloading / reloading my<br>
> drivers (which<br>
> every so often required a hard reset as well).<br>
><br>
> But if you find anything, that would be great ;)<br>
><br>
> Gr. Jerremy<br>
><br>
><br>
> On Mon, 29 Sep 2008 11:35:03 +0200, "klaas de waal"<br>
> <<a href="mailto:klaas.de.waal@gmail.com">klaas.de.waal@gmail.com</a>> wrote:<br>
> > Hallo Jeremy,<br>
> > I have exactly the same problem with my C-1501 card: tuning<br>
> problems on<br>
> > 388<br>
> > MHz but OK on most other frequencies.<br>
> > It works OK with WIndowsXP on all frequencies including the<br>
> 388MHz, so<br>
> the<br>
> > hardware is OK and it must be a software issue.<br>
> > I have over the weekend put in a lot of printk for debugging<br>
> but have not<br>
> > found it yet.<br>
> > I will keep you updated.<br>
> ><br>
> > Groetjes,<br>
> > Klaas<br>
> ><br>
> ><br>
> > On Thu, Sep 11, 2008 at 5:50 PM, <<a href="mailto:jerremy@wordtgek.nl">jerremy@wordtgek.nl</a>><br>
> wrote:<br>
> ><br>
> >> Hi,<br>
> >><br>
> >> This issue has come up at least once a bit more then a<br>
> month ago and is<br>
> >> still present in the current release of the V4L-DVB<br>
> drivers. The<br>
> >> Technotrend C-1501 drivers are unable to get a lock on<br>
> 388Mhz (and a<br>
> > couple<br>
> >> of other frequencies, like 682Mhz and 322Mhz, but I can<br>
> only test<br>
> > 388Mhz).<br>
> >><br>
> >> The dmesg will mention an I2C timeout when this occurs, I'm<br>
> not sure if<br>
> > its<br>
> >> related (as it'll randomly give those timeouts when viewing<br>
> working<br>
> >> channels too).<br>
> >><br>
> >> I have two seperate installs of Linux (Ubuntu 8.04 64-Bit<br>
> with 1<br>
> > received<br>
> >> and Ubuntu 8.04 32-Bit with 2 receivers) which both suffer<br>
> the same<br>
> >> inability to lock onto that frequency. So its unlikely to<br>
> be a hardware<br>
> >> problem, also the Windows drivers do not seem to have any<br>
> issues.<br>
> >><br>
> >> Is anyone looking into this issue? If not, what would be<br>
> the place to<br>
> >> experiment?<br>
> >><br>
> >> Gr,<br>
> >><br>
> >> Jerremy Koot<br>
> >><br>
> >><br>
</div></div></blockquote><div><br>Hello Herman,<br><br></div></div><br>Thanks for your post. I had not seen this message<br><a href="http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025634.html" target="_blank">http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025634.html</a><br>
before. Probably a lot of work has been done since because the card worked quite OK, only on the 388MHz it failed on me.<br><br>As mentioned in an earlier post, first I got my tuner working by modifying the frequency map table tda827x_dvbt to use a different setting at 388MHz. I have now put in a frequency map table tda827x_dvbc for DVB-C tuners only. This works OK for me and it should not modify the behaviour with other non-DVB-C demodulators.<br>
With the dvb-apps/util/zap utility I get a lock on all Ziggo (Dutch cable TV provider) frequencies. With MythTV-0.21 I can receive all the channels that I am entitled to.<br><br>Remaining (non-fatal) issues are:<br><br>Error message:<br>
<b>saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer</b><br>This message comes once in a while and it happens at random places, it cannot be correlated to a single place in the tda827x code. It really seems random. I have read though a lot of traces and when this error happens it does a retry and the retry succeeds.<br>
<br>Error message:<br><b>tda827x: tda827x_config not defined, cannot set LNA gain!</b><br>This message comes on every tuning action. I think that the TT-C1501 board does not have a separate LNA outside the tuner so this is not really an error. It shoudl be possible to fill in a tda827x_config struct so that it does not give this error message. I could change the code to achieve this but I do not want to change everything at once.<br>
<br>Minor issue:<br><b>Signal strength not the same across the band.</b><br>On the frequencies I can receive (from 252MHz to 826,75MHz) there is quite a lot of signal strength variation; on MythTV display ranging from 60+ to 80+ percent, on zap output from 90 to d0 or so. On a KNC-One DVB-C card (cu1216 with tda10023 plus saa7146) the signal strength is practically constant.<br>
<br>I have attached my version of the tda827x.c driver, both as complete source and as a diff against the hg version of 10 october.<br><br>Groetjes,<br>Klaas<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
<br><br><br><br><br><br></div>