From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Luis Alves <ljalvs@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] si2157: Fix DVB-C bandwidth.
Date: Tue, 22 Jul 2014 22:12:58 +0300 [thread overview]
Message-ID: <53CEB7BA.3010408@iki.fi> (raw)
In-Reply-To: <20140722140304.79ba1bcd.m.chehab@samsung.com>
On 07/22/2014 08:03 PM, Mauro Carvalho Chehab wrote:
> Em Tue, 22 Jul 2014 17:28:07 +0100
> Luis Alves <ljalvs@gmail.com> escreveu:
>
>> That's right,
>> A few days ago I also checked that with Antti. I've also had made some
>> debugging and DVB core is in fact passing the correct bandwidth to the
>> driver.
>>
>> But the true is that it doesn't work...
>> The sample I have is a dvb-c mux using QAM128 @ 6 Mbaud (which results
>> in 7MHz bw) using 7MHz filter value will make the TS stream
>> unwatchable (lots of continuity errors).
>>
>> Can this be a hardware fault?
>> All closed source drivers I've seen are hardcoding this value to 8MHz
>> when working in dvb-c (easily seen on i2c sniffs).
>
> Could be. Well, here, the DVB-C channel operators use 6MHz-spaced channels,
> with symbol rate equal to 5,217 Kbaud. I'll see if I can test it latter
> this week with a PCTV 292e.
I could also test it against modulator. However, that patch seems to be
wrong for my eyes too. Generally speaking RF tuner needs to know
bandwidth to adjust filters on signal path. For narrow suitable is
filter, the better will be signal. If you have 7MHz filter then you
definitely want use it in a case your carrier fits that space. Larger
filter will work, but CNR is worse. If filter is too narrow and cuts
your carrier, you are not able to receive mux or at lest performance
drop notably.
What is you channel raster? Could you tell center frequencies of all
your DVB-C muxes? Could you test with 7MHz bw, but adjust center
frequency off from nominal ~0-500kHz to see if it helps.
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2014-07-22 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 11:09 [PATCH] si2157: Fix DVB-C bandwidth Luis Alves
2014-07-22 15:59 ` Matthias Schwarzott
2014-07-22 16:10 ` Mauro Carvalho Chehab
2014-07-22 16:28 ` Luis Alves
2014-07-22 17:03 ` Mauro Carvalho Chehab
2014-07-22 19:12 ` Antti Palosaari [this message]
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=53CEB7BA.3010408@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=ljalvs@gmail.com \
--cc=m.chehab@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).