On 2/10/2014 1:01 PM, Albert ARIBAUD wrote:
Hi Murali,
On Mon, 10 Feb 2014 12:22:53 -0500, Murali Karicheri
<m-kariche...@ti.com> wrote:
On 2/10/2014 3:32 AM, Albert ARIBAUD wrote:
Hi Murali,
On Fri, 7 Feb 2014 18:23:07 -0500, Murali Karicheri
<m-kariche...@ti.com> wrote:
- Resending since I missed some in the CC
This patch series add support for keystone2 SoC and K2HK EVM.
Following patches were reviewed before in this list and v1 of the
same is send with review comments incorporated:-
- tools: mkimage: add support for gpimage format
- arm: add support for arch timer
- NAND: DaVinci: allow forced disable of subpage writes
The patch below is added as a seperate patch based on comments:-
- tools: sort the entries in Makefile
Murali Karicheri (5):
tools: sort the entries in Makefile
tools: mkimage: add support for gpimage format
Is this image format required? Can't one of the existing image formats
be used?
Alebert,
Thanks for your response.
We are actually re-using part of the OMAP image format by factoring out
the common code
and re-using. So this is not a new format. Please review the code.
Thanks. This describes what you do and how you do it, but it does not
tell me why you are doing it and why you can't do otherwise. Let me
rephrase my question since you're mentioning branching off the OMAP
image format: why branch off? Why not simply use the existing OMAP image
format? Or another one?
Because the ROM bootloader in our platform (keystone2) expect the header
to be in
the following format :-
<size - 4 byte> <load addr- 4 byte> <data>
OMAP uses different format
<omap header 512 bytes> <size - 4 byte> <load addr - 4 bytes>
gp header (size, loadaddr) is common between the two image formats. So that
is factored out and used in our platform. Hope this is clear now.
Regards,
Murali
Murali
Amicalement,
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
