From: Lou Otway <louis.otway@tripleplay-services.com>
To: Manu <eallaud@gmail.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Manu Abraham <abraham.manu@gmail.com>
Subject: Re: Symbol rate limit for TT 3200
Date: Wed, 23 Sep 2009 15:36:36 +0100 [thread overview]
Message-ID: <4ABA3274.4020407@tripleplay-services.com> (raw)
In-Reply-To: <1236276271.7491.1@manu-laptop>
Manu wrote:
> Hi all,
> I have been struggling for quite a while to lock on a DVB-S2
> transponder. And recently I got some information that they changed the
> symbol rate to 45MS/s which looks borderline to me. Can someone confirm
> that the TT 3200 can do that?
> I also attach a log that I obtained when trying to lock on this
> transponder with the following parameters:
> QPSK, FEC= 5/6, 45MS/s
> The driver I used was Igor's (very recent) one with szap-s2. The status
> oscillates between 00 and 0b, it can take long to attain 0b which
> suggests long and unreliable lock (never got VITERBI, just demod lock
> +sync).
> Thx for any help
> Bye
> Emmanuel
> --
>
I've been having a similar problem and have tried using the patch from
Igor Liplianin.
http://marc.info/?l=linux-dvb&m=122730082915638&w=2
Unfortunately this patch didn't work for my device until I reduced
hi_clk to 110MHz.
I'm concious that Manu Abraham (to avoid confusion with the OP, also
called Manu) doesn't recommend a frequency higher than 99MHz.
Is this a device limitation? What are the chances of damaging the device
by setting a clock frequency higher than 99MHz?
Many thanks,
Lou
next prev parent reply other threads:[~2009-09-23 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 18:04 Symbol rate limit for TT 3200 Manu
2009-09-23 14:36 ` Lou Otway [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 18:06 Manu
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=4ABA3274.4020407@tripleplay-services.com \
--to=louis.otway@tripleplay-services.com \
--cc=abraham.manu@gmail.com \
--cc=eallaud@gmail.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox