From: Arthur Konovalov <artlov@gmail.com>
To: <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] TechnoTrend C-1501 - Locking issues on 388Mhz
Date: Fri, 10 Oct 2008 12:32:16 +0300 [thread overview]
Message-ID: <48EF2120.5070101@gmail.com> (raw)
In-Reply-To: <7b41dd970810091315h1433fa7du56e5754a1684019d@mail.gmail.com>
klaas de waal wrote:
> I have the Technotrend C-1501 now locking at 388MHz.
> The table tda827xa_dvbt contains the settings for each frequency segment.
> The frequency values (first column) are for the frequency plus the IF,
> so for 388MHz
> this is 388+5 gives 393 MHz. The table starts a new segment at 390MHz,
> it then
> starts to use VCO2 instead of VCO1.
> I have now (hack, hack) changed the segment start from 390 to 395MHz so
> that the 388MHz is still tuned with VCO1, and this works OK!!
> Like this:
>
> static const struct tda827xa_data tda827xa_dvbt[] = {
> { .lomax = 56875000, .svco = 3, .spd = 4, .scr = 0, .sbs = 0, .gc3
> = 1},
> { .lomax = 67250000, .svco = 0, .spd = 3, .scr = 0, .sbs = 0, .gc3
> = 1},
> { .lomax = 81250000, .svco = 1, .spd = 3, .scr = 0, .sbs = 0, .gc3
> = 1},
> { .lomax = 97500000, .svco = 2, .spd = 3, .scr = 0, .sbs = 0, .gc3
> = 1},
> { .lomax = 113750000, .svco = 3, .spd = 3, .scr = 0, .sbs = 1, .gc3
> = 1},
> { .lomax = 134500000, .svco = 0, .spd = 2, .scr = 0, .sbs = 1, .gc3
> = 1},
> { .lomax = 154000000, .svco = 1, .spd = 2, .scr = 0, .sbs = 1, .gc3
> = 1},
> { .lomax = 162500000, .svco = 1, .spd = 2, .scr = 0, .sbs = 1, .gc3
> = 1},
> { .lomax = 183000000, .svco = 2, .spd = 2, .scr = 0, .sbs = 1, .gc3
> = 1},
> { .lomax = 195000000, .svco = 2, .spd = 2, .scr = 0, .sbs = 2, .gc3
> = 1},
> { .lomax = 227500000, .svco = 3, .spd = 2, .scr = 0, .sbs = 2, .gc3
> = 1},
> { .lomax = 269000000, .svco = 0, .spd = 1, .scr = 0, .sbs = 2, .gc3
> = 1},
> { .lomax = 290000000, .svco = 1, .spd = 1, .scr = 0, .sbs = 2, .gc3
> = 1},
> { .lomax = 325000000, .svco = 1, .spd = 1, .scr = 0, .sbs = 3, .gc3
> = 1},
> #ifdef ORIGINAL // KdW test
> { .lomax = 390000000, .svco = 2, .spd = 1, .scr = 0, .sbs = 3, .gc3
> = 1},
> #else
> { .lomax = 395000000, .svco = 2, .spd = 1, .scr = 0, .sbs = 3, .gc3
> = 1},
> #endif
> { .lomax = 455000000, .svco = 3, .spd = 1, .scr = 0, .sbs = 3, .gc3
> = 1},
> etc etc
Is it patched only in this place or somewhere else?
I tried it to solve 386MHz tuning problem, but it doesn't help.
Got LOCK, but no picture.
Arthur
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-10-10 9:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7b41dd970809290235x48f63938ic56318ba3064a71b@mail.gmail.com>
[not found] ` <c4d80f839f7e2e838b04f6c37c68d9c0@10.0.0.2>
2008-10-09 20:15 ` [linux-dvb] TechnoTrend C-1501 - Locking issues on 388Mhz klaas de waal
2008-10-10 0:36 ` hermann pitton
2008-10-12 20:21 ` klaas de waal
2008-10-13 19:27 ` Arthur Konovalov
2008-10-14 7:27 ` klaas de waal
2008-10-14 10:56 ` Arthur Konovalov
2008-10-17 9:57 ` Arthur Konovalov
2009-02-25 20:42 ` erik
2009-02-27 5:35 ` hermann pitton
2009-03-24 22:14 ` klaas de waal
2009-03-25 1:38 ` Christian Lyra
2009-03-25 21:25 ` klaas de waal
2008-10-10 9:32 ` Arthur Konovalov [this message]
2009-03-25 20:53 klaas de waal
2009-03-26 23:51 ` hermann pitton
2009-03-27 0:09 ` Mauro Carvalho Chehab
2009-03-27 0:46 ` hermann pitton
2009-03-27 1:02 ` Mauro Carvalho Chehab
2009-03-27 1:39 ` hermann pitton
2009-03-27 10:38 ` Mauro Carvalho Chehab
2009-03-27 23:23 ` hermann pitton
2009-03-28 3:03 ` hermann pitton
2009-03-28 3:58 ` Mauro Carvalho Chehab
2009-03-28 4:32 ` hermann pitton
2009-03-28 4:48 ` hermann pitton
2009-03-28 5:51 ` hermann pitton
-- strict thread matches above, loose matches on Subject: below --
2008-09-11 15:50 jerremy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EF2120.5070101@gmail.com \
--to=artlov@gmail.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.