[linux-dvb] Re: [PATCH] Another one for the Kworld-ATSC110

[Michael Krufky]

maillist wrote:
> The driver doesn't burn the new firmware to the eeprom,  as far as I can 
> tell, it doesn't even check what is already loaded. My speculation is 
> that it is uploading it to the RAM of the nxt2004 because it does a lot 
> of halts and resets to the processor after the upload. I do not believe 
> that the nxt2004 driver or the saa7134 driver is able to identify that 
> KS007 IC which I too believe is an eeprom on the serial bus.
> 
> When I replaced the "normal" firmware retrieved by the script with what 
> I extracted from the windows driver the firmware was loaded to the 
> nxt2004 but I could no longer tune any ATSC channels. The lock would 
> come and go. So either I didn't get the number of bytes extract right, 
> or this causes some changes to the interface.
> 
> Interesting claim in this forum that they received new firmware that 
> isn't available publicly yet: 
> http://forums.gbpvr.com/showpost.php?p=88231&postcount=14

Curt-

What's the problem?  Why can't you just use the current nxt2004 firmware 
provided by the get_dvb_firmware script?  It works fine on AVerTV HD 
A180 and ATi HDTV Wonder, and you SAID it was working with the patch 
that has been merged into the v4l-dvb master repository... Why re-invent 
the wheel?

If there are still bugs, PLEASE state them.

-Mike