> [1] http://tinyurl.com/2fx73a (this is a *really* early stage > software, so, probabily it won't works correctly)
Uh oh, I forgot to comment this last line :) I'm glad to see your work based on my documentation. I hardly dislike python, but reading your source, looks like most of the algorithm is easily understandable thanks to structures field names and concepts using the '0xFFFF names' (like the 'piece', piece-type:file, etc..) I recommend you to split all the fiasco format stuff out of a library or use 0xFFFF externally to avoid incompatibilities if they change the format in the future or so. FIASCO is not a good format for firmwares, checksumming is poor, extensibility is limited to the flasher tool and it's proprietary, so I would rather prefer to use tar/gz or zip just defining a clean filesystem inside for storing different pieces and metadata. Mamona project is (imho) the only one capable to define a "standard" like this one, so.. what do you think about that? I know that this is not prioritary. I'm looking forward for testing Mamona asap, it looks like an interesting project with great advantages in front of the current official one. --pancake _______________________________________________ 0xffff mailing list 0xffff@lists.nopcode.org https://lists.nopcode.org/mailman/listinfo/0xffff
