From: Antti Palosaari <crope@iki.fi>
To: Matthias Schwarzott <zzam@gentoo.org>, linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] si2165: Add first driver version
Date: Wed, 25 Dec 2013 07:20:39 +0200 [thread overview]
Message-ID: <52BA6B27.2040401@iki.fi> (raw)
In-Reply-To: <1386918133-21628-3-git-send-email-zzam@gentoo.org>
Moi Matthias
On 13.12.2013 09:02, Matthias Schwarzott wrote:
> DVB-T: works with 8MHz BW channels in germany
> DVB-C: works with QAM256
I didn't tested with a modulator, but only live signals. DVB-T seems to
work. DVB-C didn't find any channels. Symbol rate is 6875000 and both
QAM128 and QAM256 modulations. I suspect symbol rate... Symbol rate is
like a bandwidth in case of DVB-T (bw could be calculated easily from sr
just adding rolloff factor).
> TODO:
> - Extract firmware into file
Check from windows driver how it is there. There is many tricks to do
that, but I prefer hexdump.
hexdump -C WinDriver.sys | grep "AA BB CC"
hexdump -s 0x27588 -n 20000 -e '63/1 "%02x "' -e '"\n"' WinDriver.sys
After that implement extractor to get_dvb_firmware script.
> - Verify lock is correctly detected
> - Strength and Noise reporting
Statistics are not mandatory, you could implement later. Signal strength
is difficult task for demod. That could be done using RF and IF AGC
feedbacks, but it is still very rough estimate. AGC feedbacks are also
very much RF tuner dependent.
> - Set correct bandwidth / qam parameters
That was likely reason DVB-C didn't worked :)
> - what dvb-c standard is to be announced
Annex A is normal DVB-C, with 8 MHz BW.
There is also Annex B and C, another was 6 MHz BW and the other has a
little bit different rolloff factor. IIRC B is 6MHz and C is like A, but
different rolloff.
> - Compiler warnings
yeah, tons of those. Kernel has also tool for checking style etc. issues
scripts/checkpatch.pl. You must use it too.
You have put all logic to single file. It looks like that chips has
integrated two physically rather separately demods, one for DVB-T and
one for DVB-C. If there is not much registers that are programmed just
similarly in both cases, please consider splitting DVB-C and DVB-T to
own files (and maybe one file for general stuff and select weather to
call T or C). Driver is even now quite big, almost 3000 LOC in that
single file.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-12-25 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 7:02 [RFC PATCH 0/3] wintv hvr 930c-hd: Add limited support for DVB-C and DVB-T Matthias Schwarzott
2013-12-13 7:02 ` [RFC PATCH 1/3] cx231xx: Add entry for wintv 930c-hd (pid=b130) with eeprom, no dvb support Matthias Schwarzott
2013-12-13 7:02 ` [RFC PATCH 2/3] si2165: Add first driver version Matthias Schwarzott
2013-12-25 5:20 ` Antti Palosaari [this message]
2014-03-22 16:31 ` Antti Palosaari
2014-03-23 20:47 ` Matthias Schwarzott
2014-04-24 8:37 ` Antti Palosaari
2013-12-13 7:02 ` [RFC PATCH 3/3] cx231xx: add wintv 930c hd dvb support Matthias Schwarzott
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=52BA6B27.2040401@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=zzam@gentoo.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.