On Tue, 2009-06-30 at 22:09 +0100, Steve Firth wrote:
> Andy,
>          I  think that I got this wrong.......


Steve,

Well, you just went beyond what you needed to do...

> I copied and executed 
> 
>   ./get_dvb_firmware.pl  cx18 (I probably should not have done this?)

You didn't need to do that.  I shouldn't have hurt though.

> ./get_dvb_firmware.pl  mpc718

That's what you needed to do.

> and ended up with the following files
> 
> v4l-cx23418-dig.fw
> v4l-cx23418-apu.fw 
> dvb-cx18-mpc718-mt352.fw  
> v4l-cx23418-cpu.fw
> Yuan MPC718 TV Tuner Card 2.13.10.1016.zip

The v4l-cx23418* files you should have already had - no harm done.

the  "dvb-cx18-mpc718-mt352.fw" is the new one we needed.  The
get_dvb_firmware script automatically downloaded the Windows driver zip
archive and automatically snipped the dvb-cx18-mpc718-mt352.fw file out
of a file from the *zip archive.


> I copied dvb-cx18-mpc718-mt352.fw  to /lib/firmware

Good.  As long as it is where your other firmware for the CX23418 is
located.


> ---------------------------------------------------------------------
> 
> I then unzipped Yuan....zip
> 
> and ended up with these files
> 
> drvInstall.ini  h  mpc718_32bit  mpc718_64bit  setall.txt  setup.exe
> Usage.txt
> 
>     in the unzip-created sub directory.

No need for this.  That is the Windows driver archive.


> ---------------------------------------------------------------------------------------------
> 
> 
> I then followed the instructions in Usage.txt which stated that I run
> 
> 
> ./DPInst_Setup.exe 1000 1 /s 
> 
> 
> this is where I started to get a bit confused. 
> 
> I assume that this meant the "DPINnst.exe" in sub-dir mpc718_32bit not
> the Setup.exe in the current directory .....?
> (I didn't find a DPInst_Setup.exe)
> 
> This would not run, I got the following error message and could not
> proceed further
> 
> run-detectors: unable to find an interpreter for  ./DPInst_Setup.exe 

Well, those are Windows executables to install a Windows driver.  Again,
we don't need any of those.

The get_dvb_firmware script automatically

 - downloads the Windows driver archive,
 - unzips it to a tmp directory,
 - snips a string of bytes out of one file,
 - makes our dvb-cx18-mpc718-mt352.fw file, and then
 - cleans up the tmp directory.

The get_dvb_firmware script leaves the copy of the zip file lying around
so you don't have to download the zip file again, in case you ever run
the get_dvb_firmware script again.


> Was this what you expected me to run?

No.  Just the get_dvb_firmware script to get our
dvb-cx18-mpc718-mt352.fw firmware image created, and then copy it
to /lib/firmware.


> 2. Compile, install, and test the updated cx18 driver from that repo. 
> 
> Which I expected to find in the zip archive. As I said I got somewhat
> confused at this stage.

No.  When I said "that repo", I meant all the latest changes from:

        http:/linuxtv.org/hg/~awalls/cx18-mpc718

Sorry for the confusion.

Those latest changes look for the "dvb-cx18-mpc718-mt352.fw" file to
load and initialize the MT352 DVB-T demodulator chip.

It has to be done this way to avoid any software license problems.  The
information to properly initialize the MT352 is not publicly available,
and we musn't hardcode into the Linux kernel an initialization sequence
extracted from the Windows driver.

What you have tested previously and have reported as working, *cannot*
be included in the Linux kernel.  These latest changes in my cx18-mpc718
repo *can* be included in the Linux kernel.

Regards,
Andy

> P.S : I've sent my full dmesg to you under seperate cover. 
> 
> Steve



_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to