Mailing List Archive

cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?)
On Tue, 2009-06-23 at 17:49 -0400, Andy Walls wrote:
> On Tue, 2009-06-23 at 16:59 +0100, Steve Firth wrote:
> > Just another quick update.
> >
> > I've now reinstalled the 2nd tuner card back into the ACER 500, and I
> > can confirm that the patched drivers for the Yuan MPC718 work fine on
> > DVB-T both inside and outside of mythtv.
>
> Glad to hear it's working.

> > I don't know how your release procedures work or if further testing or
> > trials are needed but if you require me to do any e.g. regression
> > testing just let me know
>
> I'd like to get 2 more things done:
>
> 1. Get the EEPROM dump working for the MPC-718 working properly. It
> will hopefully be useful for identifying variants of the card in the
> future.
>
> 2. Change the function to init the mt352 DVB-T demodulator to read in a
> "firmware" file. The init sequence in my repository was extracted from
> the windows driver. I strongly believe I cannot have that committed to
> the Linux kernel, even though it is only 46 bytes from a 143 kilobyte
> file. I will also have to write an extraction tool to pull the sequence
> out of the windows binary and put instructions on a wiki page.
>
>
> I will need you to test both of these changes when I'm ready.

Steve,

To ensure MPC-718 DVB-T support can be included in the Linux kernel, I
have checked in changes to my MPC-718 development repo to:

1. extract a "firmware" sequence from the MPC-718 Windows driver
2. load that firmware in the cx18 driver to help init the MT352 on the
MPC-718

See

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



Please test it when you can

1. Run the get_dvb_firmware script with my changes from that repo and
install the new firmware file:

$ cd cx18-mpc718
$ chmod u+x linux/Documentation/dvb/get_dvb_firmware
$ linux/Documentation/dvb/get_dvb_firmware mpc718
$ sudo cp dvb-cx18-mpc718-mt352.fw /lib/firmware (or wherever for your distro)

2. Compile, install, and test the updated cx18 driver from that repo.


Once we know it works for you, I can build a cleaned up patch set and
ask for it to be pulled to the main v4l-dvb repo.

I'd still like to fix (and have you test) the EEPROM dump after we know
the DVB-T changes are good.


Regards,
Andy



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Andy,
I think that I got this wrong.......

I copied and executed

./get_dvb_firmware.pl cx18 (I probably should not have done this?)
./get_dvb_firmware.pl mpc718

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

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

---------------------------------------------------------------------

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.

---------------------------------------------------------------------------------------------


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

Was this what you expected me to run? Your instructions stated

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.

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

Steve
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
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
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Andy Walls wrote:
> 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.


you said

"we musn't hardcode into the Linux kernel an initialization sequence
extracted from the Windows driver"

this caught my attention. the kernel probably has other code like that
in it. can you explain the reasoning behind that statement?
--
simon

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Hi Andy,
Thanks for the clarification, I now have a better idea of what you're trying to achieve here.

I think that the new repo worked but I need to do some more work.

Compilation/installation worked fine. I see /dev/dvb/adaptor*/...... devices mounted correctly. But I cannot tune
in one of my cards I get a "No tables" and timeout error on the one card. Hope I haven't popped it earlier!

I did see video on the second tuner card, but there was no sound. I think I now have some problems unrelated to your firmware trials
which I need to address, I'll take a more detailed look as soon as possible.

Question: How can I be sure that I'm now really using the latest firmware not the original ones?


Steve


----- Original message -----
Sent: 2009/07/01 20:37:17
Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?)

Andy Walls wrote:
> 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.
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
On Wed, 2009-07-01 at 20:37 +0100, Simon Kenyon wrote:
> Andy Walls wrote:
> > 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.
>
>
> you said
>
> "we musn't hardcode into the Linux kernel an initialization sequence
> extracted from the Windows driver"
>
> this caught my attention. the kernel probably has other code like that
> in it. can you explain the reasoning behind that statement?

Simon,

For patches I contribute to the kernel, I essentially have to attest:

http://www.linuxtv.org/wiki/index.php/Development:_Submitting_Patches#Developer.27s_Certificate_of_Origin_1.1

with the software license in question being the GPLv2.


Given that:

1. I, along with most Linux users, don't have license to use the Yuan
MPC718 Windows driver software since I (we) don't own a Yuan MPC718
device

2. The Yuan MPC718 Windows driver likely (I haven't checked nor will I
bother) has an EULA agreement that asserts rights and restrictions
regarding use of the Windows driver binary

3. The Yuan MPC718 Windows driver binary is covered US and international
copyright laws (although 48 bytes out of ~150K may be "fair use")

I deemed (i.e. my personal belief) hardcoding a binary sequence
extracted from the Windows driver into the Linux kernel patch, puts the
patch on very shaky ground legally. I cannot make the attestation
needed for a "Signed-off-by" as outline in the Developer's Ceritifcate
of Origin.

If I could have snooped the initialization sequence via a PCI or I2C bus
monitoring mechanism with the actual hardware in my possession, that may
have been different. But that was not the case here.


If you look at the tuner-xc2028 module and the xc2028 firmware file,
you'll see the exact same process is in place. That "firmware" file is
a collection of sniipets pulled out of a Windows driver binary. The
tuner-xc2028 module won't work without it.


As for the rest of the kernel? I don't know. Check the mailing list
archives for various subsystems. I know the video4linux or linux-dvb
list went through some debate with the past year or so. I think the
resolution was to get firmware, that was coded in C arrays, out of the
kernel, so that there is no question of distribution rights under the
GPLv2.

Regards,
Andy


> simon



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
On Wed, 2009-07-01 at 22:36 +0100, Steve Firth wrote:
>
> Hi Andy,
> Thanks for the clarification, I now have a better idea of what
> you're trying to achieve here.
>
> I think that the new repo worked but I need to do some more work.
>
> Compilation/installation worked fine. I see /dev/dvb/adaptor*/......
> devices mounted correctly. But I cannot tune
> in one of my cards I get a "No tables" and timeout error on the one
> card. Hope I haven't popped it earlier!
>
> I did see video on the second tuner card, but there was no sound. I
> think I now have some problems unrelated to your firmware trials
> which I need to address, I'll take a more detailed look as soon as
> possible.
>
> Question: How can I be sure that I'm now really using the latest
> firmware not the original ones?

The original v4l-cx23418-* firmware files are still nedded.


To see if the new, additional dvb-cx18-mpc718-mt352.fw file is being
used, hmm....

On my kernel, the kernel would emit something like:

"firmware: requesting dvb-cx18-mpc718-mt352.fw"

at the "info" level in dmesg or /var/log/messages.


And following that, you *should not* see something like this in dmesg
or /var/log/messages being emitted by the cx18 driver:

"Unable to open firmware file dvb-cx18-mpc718-mt352.fw"

"Firmware dvb-cx18-mpc718-mt352.fw has a bad size: 100 bytes"

"The MPC718 board variant with the MT352 DVB-T demodualtor will not work without it"
"Run 'linux/Documentation/dvb/get_dvb_firmware mpc718' if you need the firmware"

"frontend initialization failed"


Regards,
Andy

> Steve
>
>
> ----- Original message -----
> Sent: 2009/07/01 20:37:17
> Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load needs
> testing (Re: Acer aspire idea 500?)
>
> Andy Walls wrote:
> > 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.
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Andy Walls wrote:

> If I could have snooped the initialization sequence via a PCI or I2C bus
> monitoring mechanism with the actual hardware in my possession, that may
> have been different. But that was not the case here.

that is fine.

i thought (wrongly) that you were saying that information gathered from
watching the operation of the windows binary (snooping) was at issue and
that was what was causing me concern.

keep up the good work
--
simon

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Andy

I've fixed the problem with my tuners, ....... (my mythtv SQL database simply {ahem....} needed to be repaired).

.....so now back to the plot.......


I've extracted the .fw as mentioned previously and copied it to /lib/firmware

I've loaded/compiled/installed the "repo".

I've re-tuned both cards and I can report that everything seems to work again. Cards are recognised,
there are no error messages (that I can see) in dmesg or /var/log/messages.

Summary : I can watch DVB-T on the ACER Idea 500 using your last repo


Is there any other verification that I need to do ? (EEPROM notwithstanding, which I know you still want me to do)

I've included "grep mt3" sections of messages and dmesg below. If you prefer the full files I can send them
under seperate cover. I tried "grep-ing" for cx18 but the filesize was above the limit


>>grep mt3 messages dmesg_2ndJulacer500_repo

messages:Jul 2 18:00:02 Cinema kernel: [ 1729.925082] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:00:30 Cinema kernel: [ 1757.601593] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:00:30 Cinema kernel: [ 1757.650917] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:00:56 Cinema kernel: [ 1783.216400] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:01:20 Cinema kernel: [ 1806.985972] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:01:20 Cinema kernel: [ 1807.019274] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:03:33 Cinema kernel: [ 1940.822311] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:07:34 Cinema kernel: [ 2181.400237] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:12:00 Cinema kernel: [ 2447.921560] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:12:00 Cinema kernel: [ 2448.071017] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:16:12 Cinema kernel: [ 32.208000] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
messages:Jul 2 18:16:14 Cinema kernel: [ 34.228119] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
dmesg_2ndJulacer500_repo:[ 32.205722] mt352: mt352_init: hello
dmesg_2ndJulacer500_repo:[ 32.208000] cx18 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
dmesg_2ndJulacer500_repo:[ 32.276915] mt352: mt352_calc_nominal_rate: bw 8, adc_clock 20480 => 0x7249
dmesg_2ndJulacer500_repo:[ 32.276920] mt352: mt352_calc_input_freq: if2 4560, ife 4560, adc_clock 20480 => -3645 / 0x31c3
dmesg_2ndJulacer500_repo:[ 34.225843] mt352: mt352_init: hello
dmesg_2ndJulacer500_repo:[ 34.228119] cx18 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw





----- Original message -----
Sent: 2009/07/02 00:25:36
Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?)

On Wed, 2009-07-01 at 22:36 +0100, Steve Firth wrote:
>
> Hi Andy,
> Thanks for the clarification, I now have a better idea of what
> you're trying to achieve here.
>
> I think that the new repo worked but I need to do some more work.
>
> Compilation/installation worked fine. I see /dev/dvb/adaptor*/......
> devices mounted correctly. But I cannot tune
> in one of my cards I get a "No tables" and timeout error on the one
> card. Hope I haven't popped it earlier!
>
> I did see video on the second tuner card, but there was no sound. I
> think I now have some problems unrelated to your firmware trials
> which I need to address, I'll take a more detailed look as soon as
> possible.
>
> Question: How can I be sure that I'm now really using the latest
> firmware not the original ones?

The original v4l-cx23418-* firmware files are still nedded.


To see if the new, additional dvb-cx18-mpc718-mt352.fw file is being
used, hmm....

On my kernel, the kernel would emit something like:

"firmware: requesting dvb-cx18-mpc718-mt352.fw"

at the "info" level in dmesg or /var/log/messages.


And following that, you *should not* see something like this in dmesg
or /var/log/messages being emitted by the cx18 driver:

"Unable to open firmware file dvb-cx18-mpc718-mt352.fw"

"Firmware dvb-cx18-mpc718-mt352.fw has a bad size: 100 bytes"

"The MPC718 board variant with the MT352 DVB-T demodualtor will not work without it"
"Run 'linux/Documentation/dvb/get_dvb_firmware mpc718' if you need the firmware"

"frontend initialization failed"


Regards,
Andy

> Steve
>
>
> ----- Original message -----
> Sent: 2009/07/01 20:37:17
> Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load needs
> testing (Re: Acer aspire idea 500?)
>
> Andy Walls wrote:
> > 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.
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
On Thu, 2009-07-02 at 18:45 +0100, Steve Firth wrote:
> Andy
>
> I've fixed the problem with my tuners, ....... (my mythtv SQL
> database simply {ahem....} needed to be repaired).
>
> .....so now back to the plot.......
>
>
> I've extracted the .fw as mentioned previously and copied it
> to /lib/firmware
>
> I've loaded/compiled/installed the "repo".
>
> I've re-tuned both cards and I can report that everything seems to
> work again. Cards are recognised,
> there are no error messages (that I can see) in dmesg
> or /var/log/messages.
>
> Summary : I can watch DVB-T on the ACER Idea 500 using your last
> repo
>

OK, good. I'll assemble a cleaned-up patch for the DVB-T and basic
board support and have it pulled to the main v4l-dvb repository.



> Is there any other verification that I need to do ? (EEPROM
> notwithstanding, which I know you still want me to do)

Not at the moment, unless you really want to use, and hence are
motivated to test, the various analog inputs: CVBS, SVideo, audio line
in.

I don't needed 7 MHz DVB-T tested yet either. The latest v4l-dvb just
pulled a patch I made for the XC3028 for 7 MHz DVB-T. So if, you test 7
MHz DVB-T right now and run into any problems, I'm just going to tell
you to wait until everything makes it to the main v4l-dvb repository.

In the near future, I'll give you one more patch for the EEPROM dump, to
see if I can get that right this time. :)


> I've included "grep mt3" sections of messages and dmesg below. If
> you prefer the full files I can send them
> under seperate cover. I tried "grep-ing" for cx18 but the filesize was
> above the limit
>
>
> >>grep mt3 messages dmesg_2ndJulacer500_repo
>
> messages:Jul 2 18:00:02 Cinema kernel: [ 1729.925082] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:00:30 Cinema kernel: [ 1757.601593] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:00:30 Cinema kernel: [ 1757.650917] cx18
> 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:00:56 Cinema kernel: [ 1783.216400] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:01:20 Cinema kernel: [ 1806.985972] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:01:20 Cinema kernel: [ 1807.019274] cx18
> 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:03:33 Cinema kernel: [ 1940.822311] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:07:34 Cinema kernel: [ 2181.400237] cx18
> 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:12:00 Cinema kernel: [ 2447.921560] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:12:00 Cinema kernel: [ 2448.071017] cx18
> 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:16:12 Cinema kernel: [ 32.208000] cx18
> 0000:02:00.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> messages:Jul 2 18:16:14 Cinema kernel: [ 34.228119] cx18
> 0000:02:01.0: firmware: requesting dvb-cx18-mpc718-mt352.fw
> dmesg_2ndJulacer500_repo:[ 32.205722] mt352: mt352_init: hello
> dmesg_2ndJulacer500_repo:[ 32.208000] cx18 0000:02:00.0: firmware:
> requesting dvb-cx18-mpc718-mt352.fw
> dmesg_2ndJulacer500_repo:[ 32.276915] mt352:
> mt352_calc_nominal_rate: bw 8, adc_clock 20480 => 0x7249
> dmesg_2ndJulacer500_repo:[ 32.276920] mt352: mt352_calc_input_freq:
> if2 4560, ife 4560, adc_clock 20480 => -3645 / 0x31c3
> dmesg_2ndJulacer500_repo:[ 34.225843] mt352: mt352_init: hello
> dmesg_2ndJulacer500_repo:[ 34.228119] cx18 0000:02:01.0: firmware:
> requesting dvb-cx18-mpc718-mt352.fw

Hmmm. What events trip those firmware loads: channel changes, or
open/close, or something else? I wasn't quite sure how often the mt352
driver module would call my init function. If it's excessively going
back and forth to the filesystem, I may work up something to cache the
firmware (it's only 48 bytes or so).



Regards,
Andy

>
>
>
>
> ----- Original message -----
> Sent: 2009/07/02 00:25:36
> Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load needs
> testing (Re: Acer aspire idea 500?)
>
> On Wed, 2009-07-01 at 22:36 +0100, Steve Firth wrote:
> >
> > Hi Andy,
> > Thanks for the clarification, I now have a better idea of what
> > you're trying to achieve here.
> >
> > I think that the new repo worked but I need to do some more work.
> >
> > Compilation/installation worked fine. I
> see /dev/dvb/adaptor*/......
> > devices mounted correctly. But I cannot tune
> > in one of my cards I get a "No tables" and timeout error on the one
> > card. Hope I haven't popped it earlier!
> >
> > I did see video on the second tuner card, but there was no sound. I
> > think I now have some problems unrelated to your firmware trials
> > which I need to address, I'll take a more detailed look as soon as
> > possible.
> >
> > Question: How can I be sure that I'm now really using the latest
> > firmware not the original ones?
>
> The original v4l-cx23418-* firmware files are still nedded.
>
>
> To see if the new, additional dvb-cx18-mpc718-mt352.fw file is being
> used, hmm....
>
> On my kernel, the kernel would emit something like:
>
> "firmware: requesting dvb-cx18-mpc718-mt352.fw"
>
> at the "info" level in dmesg or /var/log/messages.
>
>
> And following that, you *should not* see something like this in dmesg
> or /var/log/messages being emitted by the cx18 driver:
>
> "Unable to open firmware file dvb-cx18-mpc718-mt352.fw"
>
> "Firmware dvb-cx18-mpc718-mt352.fw has a bad size: 100 bytes"
>
> "The MPC718 board variant with the MT352 DVB-T demodualtor will not
> work without it"
> "Run 'linux/Documentation/dvb/get_dvb_firmware mpc718' if you need the
> firmware"
>
> "frontend initialization failed"
>
>
> Regards,
> Andy
>
> > Steve
> >
> >
> > ----- Original message -----
> > Sent: 2009/07/01 20:37:17
> > Subject: Re:Re: [ivtv-devel] cx18: MPC718 MT352 "firmware" load
> needs
> > testing (Re: Acer aspire idea 500?)
> >
> > Andy Walls wrote:
> > > 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.
> >
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
On Thu, 2009-07-02 at 15:22 -0400, Andy Walls wrote:
> On Thu, 2009-07-02 at 18:45 +0100, Steve Firth wrote:
> >
> > Summary : I can watch DVB-T on the ACER Idea 500 using your last
> > repo
> >
>
> OK, good. I'll assemble a cleaned-up patch for the DVB-T and basic
> board support and have it pulled to the main v4l-dvb repository.
>
>
>
> > Is there any other verification that I need to do ? (EEPROM
> > notwithstanding, which I know you still want me to do)

> In the near future, I'll give you one more patch for the EEPROM dump, to
> see if I can get that right this time. :)

Steve,

I have pushed a patch to:

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

to re-enable the eeprom dump on moudle load for the MPC718.

When you test this could you:


1. Add

options tveeprom debug=1

to your /etc/modprobe.conf (or whatever your distro uses).

2. 'make unload' to make sure the tveeprom module and all old v4l-dvb
modules are unloaded from memory.

3. Then load the cx18 module as you normally do. It will load the
tveeprom module on it's own, but this time the debug option will be set
for the tveeprom module.

I'd like to see what gets logged by both the tveeprom module and the
cx18 module when the cx18 driver is loaded. I can't see why my previous
effort to dump the MPC718 eeprom failed, so hopefully these messages
will give me more insight.

Thanks.

Regards,
Andy


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: cx18: MPC718 MT352 "firmware" load needs testing (Re: Acer aspire idea 500?) [ In reply to ]
Done.

...... /lvar/log/messages & dmesg ogs sent direct, due to size

Steve


>>1. Add
>>
>>options tveeprom debug=1
>>
>>to your /etc/modprobe.conf (or whatever your distro uses).
>>
>>2. 'make unload' to make sure the tveeprom module and all old v4l-dvb
>>modules are unloaded from memory.
>>
>>3. Then load the cx18 module as you normally do. It will load the
>>tveeprom module on it's own, but this time the debug option will be set
>>for the tveeprom module.

>>I'd like to see what gets logged by both the tveeprom module and the
>>cx18 module when the cx18 driver is loaded. I can't see why my previous
>>effort to dump the MPC718 eeprom failed, so hopefully these messages
>>will give me more insight.

l