In message OFD9437230.22326F6B-ONC1257292.00465732-C1257292.0047638F@philips.com you wrote:
CHANGELOG:
- Add option -p to mkimage for always alligning an image to word boundary.
Images are already aligned. They have a 64 byte header prepended.
This patch adds a feature to tools/mkimage.c by making it possible to always align a filesystem image to word boundary. Images created with this option are always aligned on word boundary and will always correctly be loaded with the ARM RVDS when using raw mode (Raw data one word per word
I don't get what you're trying to tell.
Looking at your patch, it seems you're confusing padding to a multiuple of 32 bit words with alignment - note these are completely different things.
of memory). Images created without this option will not boot with u-boot and abort with "Data CRC error". This situation has been reported several times on this maillinglist.
Has it? I have never seen it. Do you have a reference?
It is tested against todays git repository.
You patch is not acceptable; the description is wrong both in the log and in the help message, it has coding style violations (indentation not by TAB etc.) and spelling errors.
Also, I'm not sure if this is really a mkimage problem.
Best regards,
Wolfgang Denk