From: "Unembossed Name" <severe.siberian.man@mail.ru>
To: <linux-media@vger.kernel.org>, "Antti Palosaari" <crope@iki.fi>
Subject: Re: Si2168 B40 frimware.
Date: Sun, 7 Jun 2015 03:02:25 +0700 [thread overview]
Message-ID: <CFB6F14A3740441FB49C6FF2FC3CAD56@unknown> (raw)
In-Reply-To: 55733133.6050502@iki.fi
From: "Antti Palosaari"
To: "Unembossed Name"
Sent: Sunday, June 07, 2015 12:43 AM
Subject: Re: Si2168 B40 frimware.
>> Anybody want to test it? Unfortunately, I can not do it myself, because
>> I do not own hardware with B40 revision.
>
> That does not even download. It looks like 17 byte chunk format, but it
> does not divide by 17. Probably there is some bytes missing or too many
> at the end of file.
>
> That is how first 16 bytes of those firmwares looks:
> 4.0.4: 05 00 aa 4d 56 40 00 00 0c 6a 7e aa ef 51 da 89
> 4.0.11: 08 05 00 8d fc 56 40 00 00 00 00 00 00 00 00 00
> 4.0.19: 08 05 00 f0 9a 56 40 00 00 00 00 00 00 00 00 00
>
> 4.0.4 is 8 byte chunks, 4.0.11 is 17 byte.
Hi Antti,
You're right. I've made a mistake with determining of the end of a patch. It seems I blindly used an obsolete information about
size it should be. And because of that, these version of a patch can be even more recent. Like 4.0.20.
Could you please check it again? And in case of success see which version it is?
file name:dvb-demod-si2168-b40-rom4_0_2-patch-build-probably4_0_19.fw.tar.gz
http://beholder.ru/bb/download/file.php?id=857
Best regards.
next prev parent reply other threads:[~2015-06-06 20:02 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 [this message]
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
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=CFB6F14A3740441FB49C6FF2FC3CAD56@unknown \
--to=severe.siberian.man@mail.ru \
--cc=crope@iki.fi \
--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 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.