From: "Unembossed Name" <severe.siberian.man@mail.ru>
To: "Devin Heitmueller" <dheitmueller@kernellabs.com>
Cc: <linux-media@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@osg.samsung.com>
Subject: Re: XC5000C 0x14b4 status
Date: Fri, 26 Jun 2015 18:51:42 +0700 [thread overview]
Message-ID: <B3C502409DDD44C1BF8B9EA021AFA3B3@unknown> (raw)
In-Reply-To: CAGoCfixD8VwQX9jB8a3_8urGu4y3D+x=JhZvq8PbpTpPcqrGzQ@mail.gmail.com
>> It's not "new" IC. It's XC5000C. Maybe i was interpreted wrong.
>> As I have understood, such behaviour can depends from FW version.
>> HW vendor says, that with his latest FW he always gets response 0x14b4.
>
> Ah, so you're running a completely different firmware image? Well in
> that case that would explain the different response for the firmware
> loaded indication.
No no no. I used a FW image, which was taken from KernelLabs site, and it
was intended for use with XC5000C. And partnumber of IC was XC5000C
( I have opened RF shild to check it)
>> Not a 0x1388. And I think, that these ICs still come without pre-loaded FW.
>> HW vendor also didn't says anything about FW pre-load possibility.
>
> Correct. These are not parts that have any form of default firmware
> in their ROM mask (i.e. not like the silabs or micronas parts which
> have a default firmware and the ability to patch the ROM via a
> software loaded code update). The firmware must be loaded every time
> the chip is brought out of reset or it won't work at all.
next prev parent reply other threads:[~2015-06-26 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:58 XC5000C 0x14b4 status Unembossed Name
2015-06-26 9:22 ` Mauro Carvalho Chehab
2015-06-26 10:59 ` Unembossed Name
2015-06-26 11:04 ` Devin Heitmueller
2015-06-26 11:21 ` Steven Toth
2015-06-26 12:19 ` Unembossed Name
2015-06-26 14:15 ` Steven Toth
2015-06-26 14:59 ` Unembossed Name
2015-06-26 11:51 ` Unembossed Name [this message]
2015-06-26 11:00 ` Devin Heitmueller
2015-06-26 11:39 ` Unembossed Name
2015-06-29 22:55 ` Unembossed Name
2015-06-30 0:42 ` Unembossed Name
2015-07-01 21:41 ` 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=B3C502409DDD44C1BF8B9EA021AFA3B3@unknown \
--to=severe.siberian.man@mail.ru \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.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