On gio, 2008-03-27 at 12:13 +0100, Luigi 'Comio' Mantellini wrote: > > > - The mkimage calculate hashes before that timestamp is added to > image. > is it better exchange the order of these operations (before add > timestamp then calculate hashes)? > - Does the new format assure that the complete image (_all_ sections, > images, ramdisks, configurations, blobs) are covered by at least an > hash > value? should mkimage add at least a hash value for the root node? >
In addition to the previous question:
- I'm interested to calculate and store from U-boot code but the
fit_image_set_hashes is compiled only when the USE_HOSTCC symbol is
defined. Why? Is there a particular reason? I think that a lot of useful
functions (ifdef-ed by USE_HOSTCC) should be available also in u-boot
code, anyway the linker will drop the unused functions.
Any comments?
thanks
luigi
Industrie Dial Face S.p.A.
Luigi Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy
Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
E-mail: [EMAIL PROTECTED]
GPG fingerprint: 3DD1 7B71 FBDF 6376
1B4A
B003 175F E979 907E
1650
<<attachment: idf_logo.gif>>
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
