Stephen Warren wrote:
> On Wed, March 12, 2008 1:35 am, Phil Dibowitz wrote:
>> All it takes is updating the first 6 bytes. If I take a
>> file from the website, update the first 6 bytes with the
>> first 6 bytes of my firmware and then use it to update my
>> remote, it works like a charm.
> 
> Are you sure those values are always constant? I.e. how do we know that
> one/more of the bytes isn't some kind of firmware-data-specific check-sum
> that'll need to be different for future firmware releases?

Possibly. It's hard to say until new firmware comes out.

> Also, looking through the firmware files in Kevin's harmony_usb_logs.zip,
> I notice that some remotes appear to have 4 * FF in the firmware downloads
> from the website, and others 6 * FF (maybe even 1 with 8 * FF?) So, I
> guess we need to parameterize the count of bytes to "keep" based on arch?

/me shrugs.

>> Note that involves changing read_firmware_from_file() quite a bit, so if
>> anyone's working on a patch that touches that, you may want to wait a bit.
> 
> Shouldn't this overwrite be performed in the write-firmware-to-remote
> function, since that deals with HW, whereas read_firmware_from_file() is
> just file IO?

No, you're confusing the "update the magic bits" patch with the "talk to the
website patch"... the update the magic bits part effects write_to.. but the
talk to the website part effects read_from...

This is because read_firmware_from_file was only grabbing binary data out of
the file. It now reads the whole file just like read_config_from_file(), and
then there's an extract_binary_firmware() to grab the hex from that and do
the conversion to binary. Otherwise I wouldn't have the rest of the XML data
necessary to talk to the website.

-- 
Phil Dibowitz                             [EMAIL PROTECTED]
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to