Skip to content

Add support for Keystone2 SoC and K2HK EVM

Albert ARIBAUD u-boot 3 versions New

Get series with b4
b4 am 20140210205810.0d680f82@lilith

Versions newest first · linked by author and title

  1. v1 Latest posting 3/30 of 7 patches 0 repliesNew
  2. v1 posting 2/30 of 7 patches 0 repliesSuperseded
  3. v1 posting 1/30 of 7 patches 0 repliesSuperseded

Patches in v1 posting 3/3 No applies recorded yet

None of the 7 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [U-Boot] [U-Boot: RESEND][PATCH 0/7] Add support for Keystone2 SoC and K2HK EVM

Hi Murali,

Quoted 46 lines · Murali Karicheri
Quoted 33 lines · Albert ARIBAUD

Hi Murali,

Quoted 28 lines · Murali Karicheri
Quoted 15 lines · Albert ARIBAUD

Hi Murali,

Quoted 10 lines · Murali Karicheri

- 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

Quoted 8 lines
Quoted 6 lines

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.

Quoted 8 lines
Quoted 3 lines

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 :-

Quoted 7 lines

<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.

Ok, thanks.

Quoted 3 lines

Regards,

Murali

Amicalement,

Signature · 1 line
Albert.