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:39:27 +0700 [thread overview]
Message-ID: <70768F550F7841098B5BC3E9EEDFB33C@unknown> (raw)
In-Reply-To: CAGoCfiyjRSxRrzdWVPREVaXoMK_iowu19n2+FJosg90UskumHA@mail.gmail.com
>> IMHO, the best is to get the latest firmware licensed is the best
>> thing to do.
>>
>> Does that "new" xc5000c come with a firmware pre-loaded already?
>
> I've got firmware here that is indicated as being for the xc5300 (i.e.
> 0x14b4). That said, I am not sure if it's the same as the original
> 5000c firmware. Definitely makes sense to do an I2C dump and compare
> the firmware images since using the wrong firmware can damage the
> part.
As I have understood, reading Poduct ID register (together with reading
checksum register) is primarily for check integrity of uploaded FW.
It's not indicates IC's P/N which FW should belong.
> I'm not against an additional #define for the 0x14b4 part ID, but it
> shouldn't be accepted upstream until we have corresponding firmware
> and have seen the tuner working. Do you have digital signal lock
> working with this device under Linux and the issue is strictly with
> part identification?
With that RF tuner IC, Linux driver and public available FW for XC5000C
(from Kernel Labs) I successfully received analog and digital transmissions
over an air. Didn't checked it with DVC-C though.
next prev parent reply other threads:[~2015-06-26 11:39 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
2015-06-26 11:00 ` Devin Heitmueller
2015-06-26 11:39 ` Unembossed Name [this message]
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=70768F550F7841098B5BC3E9EEDFB33C@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 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.