Phil Dibowitz wrote: >> c) libconcord should hard-code/calculate the first bytes 0..5 of >> firmware, not read them from flash. > > Indeed. I'm going to change this code now to something more sensible. OK, > well, after the checkin that's coming in a minute.
Well, it's not GOOD, but it's better. I've set it up to set the first 2 bytes to the right value for the latest firmware (with a huge FIXME), leave the next two bytes alone, and hard-code the 3rd pair of bytes. These changes work for me, as you'd expect. They'll only work for anyone on the latest firmware, and most likely, only for people on arch 8, but MAYBE for 3 and 7 (I haven't looked to much into those yet), but it's a step in the right direction. -- 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
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
