From: Antti Palosaari <crope@iki.fi>
To: CrazyCat <crazycat69@narod.ru>,
linux-media <linux-media@vger.kernel.org>,
Olli Salonen <olli.salonen@iki.fi>
Subject: Re: [PATCH 1/3] tuners: si2157: Si2148 support.
Date: Sat, 15 Nov 2014 03:36:41 +0200 [thread overview]
Message-ID: <5466AE29.2080502@iki.fi> (raw)
In-Reply-To: <525911416014537@web7h.yandex.ru>
On 11/15/2014 03:22 AM, CrazyCat wrote:
> 2148 is 2158 without analog support. Same firmware.
>
> 15.11.2014, 03:02, "Antti Palosaari" <crope@iki.fi>:
>> I wonder if we should define own firmware for Si2148-A20 just for sure.
>> Olli?
But still... I have seen one case where even same revision of si2168
needs different firmware. It is not very clear for me how SiLabs uses
these firmwares, but at least it seems to be:
* There is different versions done from same chips. A10 < A20 < A30 <
B40 and so. I think that means digital logic inside of chip is changed
when they change that revision number.
* Every chip has a ROM, containing default firmware. Firmware which
driver downloads is just a patch to that ROM. ROM is updated regularly
when new patch of chips are manufactured.
So currently I have feeling it is better to define as many firmware
files as there chip revisions available, even same firmware works for
multiple chip models/versions/revisions.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2014-11-15 1:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 21:19 [PATCH 1/3] tuners: si2157: Si2148 support CrazyCat
2014-11-15 1:01 ` Antti Palosaari
2014-11-15 1:22 ` CrazyCat
2014-11-15 1:36 ` Antti Palosaari [this message]
2014-11-15 10:41 ` Olli Salonen
2014-11-15 11:02 ` Antti Palosaari
2014-11-15 12:33 ` Olli Salonen
[not found] <CA++x_yD6oxb4mkbP_8UtHU13LM5dgacbtHXWKe+qpDEfFp5bMw@mail.gmail.com>
2014-11-17 16:10 ` Michael Holzer
2014-11-20 20:10 ` Olli Salonen
2014-11-20 21:07 ` CrazyCat
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=5466AE29.2080502@iki.fi \
--to=crope@iki.fi \
--cc=crazycat69@narod.ru \
--cc=linux-media@vger.kernel.org \
--cc=olli.salonen@iki.fi \
/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.