Re: When xc3028/xc2028 will be supported?

[Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>]

On Mon, 28 Jan 2008 19:22:30 -0200
Dâniel Fraga <fragabr@xxxxxxxxx> wrote:

> On Mon, 28 Jan 2008 18:45:34 -0200
> Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote:
> 
> > > cx8800: Unknown symbol v4l2_chip_match_host
> 
> > Please update the changeset from master. An experimental patch were committed
> > by mistake, together with a good patch. Sorry for the inconvenience.
> 
> 	No problem. The above error was because I messed up with
> menuconfig. Now everything is fine, except for the firmware:
> 
> 1) the extract_xc3028.pl seems to be specific for just one firmware,
> right? I have a cx88vid.sys file, but the script won't accept this file.
> 
> 2) I have firmware form Markus already. I tried to use them without
> success. For example:
> 
> xc2028 3-0061: Loading 3026 firmware images from xc3028-v27.fw, type:
> ^A^A, ver 64.193 xc2028 3-0061: Firmware type DTV8 OREN538 OREN36
> TOYOTA388 TOYOTA794 CHINA F6MHZ INPUT2 (1cf00200), id 1d01cf000d103a0
> is corrupted (size=8792, expected 64095185) xc2028 3-0061: Error:
> firmware file is corrupted! xc2028 3-0061: Releasing partially loaded
> firmware file.
> 
> 	xc3028-v27.fw was a link to the real firmware...
> 	
> 	I used these firmwares:
> 
> http://mcentral.de/firmware/
> 
> 	Powerangel
> Conexant cx23880/xc3028
> firmware_powercolor.tgz
> 
> 	They should work, right?
> 
> 	What do you suggest? Thank you very much!


The in-kernel driver approach for xc2028/xc3028 has a complex logic for loading
a firmware. The big advantage of this approach is that almost no changes are
required at the bridge drivers. Also, just one firmware file is needed for all
video/dvb/radio standards.

In order to do that, the firmware format of the in-kernel driver is completely
different from the format used by other approaches. Just one firmware file is
enough for video, radio and DVB. Internally, it will contain several small 
firmwares, for each different xc3028 supported standard. 

The driver loads all firmwares once, and will automatically load the proper part,
based on the required standard.

The only required changes at the bridge driver (cx88, in this case) is to add
a xc3028-specific setup, and to add a callback, with the reset gpio codes. 

The reset code is specific to each hardware design. Since several hardwares are
based at the same reference design, generally, the initialization code may be
the same for two different boards.

This is what the first patch does: adds the xc3028 specific setup, and creates
a callback for xc3028.

The second patch addresses the different initialization needs for some boards,
and adds the entries for the boards itself.

About the firmware, XCeive one has an internal version number. In thesis, the
firmware file can be the same for all xc3028 based boards. If you turn on debug
on tuner-xc2028, it will print the firmware internal code, after successfully
loading it.

The newest firmware, AFAIK, is version 2.7. There are some hardwares that
might require an older firmware version (this is the case of my tm6000 10moons
device, that requires firmware version 1.e). The in-kernel driver supports
older firmware, but some extracting tool is needed for older firmwares.

The windows .sys file contains the firmware + xc3028 code + device-specific
code + vendor-specific code. So, your .sys file is likely to be different
between two different cards, even if they have the same Xceive firmware version.

In your case, if your .sys is supplied with firmware version 2.7, you can
extract the firmware from hcw85bda.sys, and this should work properly for your
board.


Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list