From: "Unembossed Name" <severe.siberian.man@mail.ru>
To: <linux-media@vger.kernel.org>, "Hurda" <hurda@chello.at>
Subject: Re: Si2168 B40 frimware.
Date: Mon, 8 Jun 2015 03:55:08 +0700 [thread overview]
Message-ID: <C6841AEECECB40A2A9A6CDB7320309F9@unknown> (raw)
In-Reply-To: 557494E1.3060403@chello.at
Hi Hurda,
> What's new with that firmware?
> It's twice as big as 4.0.11, so there got to be a lot of changes and fixes.
I can't tell exactly what 4.0.19 does. May be I'm wrong, but I suppose, patch 4.0.19
for B40 has so big size, because most likely it resolves the same issues as patch 3.0.20 for A30:
Here, in Russia, TV broadcasters actively using Multi PLP in DVB-T2 transmissions.
In some cities, were problems with switching to PLP#1 or PLP#2 without A30 3.0.20 patch.
(Different cities in different time zones lead to a separate mux transport streams for them.)
What I can tell exactly, is that A30 3.0.20 contains an update for Si2168, which allows
demodulator to lock PLP#2 with an "old" type OFDM frame encoding. Also it speed up locking
for low bitrates PLP.
In short: it fixes a serious issue with Multi PLP locking.
> I assume the info originates from
> http://beholder.ru/bb/viewtopic.php?f=11&t=14101 , but I don't understand
> Russian at all.
Yes, you are right.
Best regards.
prev parent reply other threads:[~2015-06-07 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 3:28 Si2168 B40 frimware Unembossed Name
2015-06-06 17:43 ` Antti Palosaari
2015-06-06 20:02 ` Unembossed Name
2015-06-06 20:14 ` Antti Palosaari
2015-06-06 20:57 ` Unembossed Name
2015-06-07 19:00 ` Hurda
2015-06-07 20:55 ` Unembossed Name [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=C6841AEECECB40A2A9A6CDB7320309F9@unknown \
--to=severe.siberian.man@mail.ru \
--cc=hurda@chello.at \
--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