Re: XC5000C 0x14b4 status

2015-07-01 Thread Unembossed Name
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

Re: XC5000C 0x14b4 status

2015-06-29 Thread Unembossed Name
I just received a confirmation, that firmware in file latest-dvb-fe-xc5000c-0.6.30.5.fw is working. xc5000: Firmware latest-dvb-fe-xc5000c-0.6.30.5.fw loaded and running xc5000: *** HW: V6.0, FW: V 0.6.40990 So, it's has a build number 40990 -- To unsubscribe from this list: send the line

Re: XC5000C 0x14b4 status

2015-06-29 Thread Unembossed Name
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

Re: XC5000C 0x14b4 status

2015-06-26 Thread Unembossed Name
Here is a link on a chinese site with datasheet for xc5100. http://wenku.baidu.com/view/7f92f3fe700abb68a982fb96.html If you look at it, after reading Product ID we also should receive 0x14b4 (5300 decimal) I'll try extract a FW from a Windows driver and will share results, in case of success.

Re: XC5000C 0x14b4 status

2015-06-26 Thread Unembossed Name
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

Re: XC5000C 0x14b4 status

2015-06-26 Thread Unembossed Name
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

Re: XC5000C 0x14b4 status

2015-06-26 Thread Unembossed Name
From: Mauro Carvalho Chehab To: Unembossed Name Cc: linux-media@vger.kernel.org; Devin Heitmueller Sent: Friday, June 26, 2015 4:22 PM Subject: Re: XC5000C 0x14b4 status After that RF tuner identification became always successful. I had a conversation with a hardware vendor. Now I can say

Re: XC5000C 0x14b4 status

2015-06-26 Thread Unembossed Name
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

XC5000C 0x14b4 status

2015-06-25 Thread Unembossed Name
Hi, I was working on a Linux driver for a hybrid TV-tuner with SAA7134 PCI bridge, XC5000C RF tuner and Si2168 DVB demodulator by a combining all existent at that time drivers together. During that work, I had an issue with XC5000C. Episodically, after attaching to DVB and reading

Re: About Si2168 Part, Revision and ROM detection.

2015-06-08 Thread Unembossed Name
From: Antti Palosaari To: Unembossed Name severe.siberian@mail.ru; linux-media@vger.kernel.org Sent: Monday, June 08, 2015 10:22 PM Subject: Re: About Si2168 Part, Revision and ROM detection. Also, I would like to suggest a following naming method for files containing firmware patches

Re: About Si2168 Part, Revision and ROM detection.

2015-06-08 Thread Unembossed Name
From: Antti Palosaari To: Unembossed Name severe.siberian@mail.ru; linux-media@vger.kernel.org Sent: Tuesday, June 09, 2015 6:46 AM Subject: Re: About Si2168 Part, Revision and ROM detection. And at the same time, he was able to successfully upload firmware patch, that designed for A30

Re: About Si2168 Part, Revision and ROM detection.

2015-06-08 Thread Unembossed Name
From: Antti Palosaari To: Unembossed Name severe.siberian@mail.ru; linux-media@vger.kernel.org Sent: Tuesday, June 09, 2015 6:46 AM Subject: Re: About Si2168 Part, Revision and ROM detection. Also, I would like to suggest a following naming method for files containing firmware patches

Re: Si2168 B40 frimware.

2015-06-07 Thread Unembossed Name
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

Re: Si2168 B40 frimware.

2015-06-06 Thread Unembossed Name
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

Re: Si2168 B40 frimware.

2015-06-06 Thread Unembossed Name
From: Antti Palosaari To: Unembossed Name severe.siberian@mail.ru; linux-media@vger.kernel.org Sent: Sunday, June 07, 2015 3:14 AM Subject: Re: Si2168 B40 frimware. 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

Si2168 B40 frimware.

2015-06-05 Thread Unembossed Name
Hi, Yesterday I extracted a new firmware for Si2168 B40 rev. from Windows driver. It's designed for ROM version 4.0.2 and has a version build 4.0.19 Here is a name of file:dvb-demod-si2168-b40-rom4_0_2-patch-build4_0_19.fw.tar.gz And a link for download:

About Si2168 Part, Revision and ROM detection.

2015-06-05 Thread Unembossed Name
Hi, Information below was given by a hardware vendor, who uses these demodulators on their dvb-t2 products. As an explanation on our questions for Si2168 Linux driver development. I think it can give more clue with Part, Revision and ROM detection algorithm in Linux driver for that