patchset2 - cleanup cont.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 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.
Cover letter [U-Boot-Users] [PATCH 0/6] [new uImage] patchset2 - cleanup cont.
Quoted 17 lines · Kumar Gala
Quoted 9 lines
This is a second patchset for new uImage, it includes architecture file renames, removals of
OF_FLAT_TREEand standalone application support and further code refactoring.This patchset is based on patchset1. MAKEALL was run for ppc/arm/mips/coldfire,
architestures, plus regression tests on lite5200b.Quoted 7 lines
[new uImage] Move FDT error printing to common
fdt_error()routine [new uImage] Factor out common routines for getting os/arch/type/comp names
[new uImage] Remove standalone applications handling from boootm [new uImage] RemoveOF_FLAT_TREEsupport from PPC bootm code [new uImage] Use image API in SHdo_bootm_linux()routine [new uImage] Rename architecture specific bootm code files
Quoted 4 lines
I haven't looked through these, but is it possible to make it so if you are using a flat device tree blob on PPC that we can grow the size dynamically as we handle some of the board fixups as part of the bootm processing?
That should be possible. It'll require to always move the blob to the new location (with the new size) - currently we move it only if needed. And, we would need to figure out what the grow delta should be, reading it from env variable (with the fallback default) should be flexible enough. But I would prefer to get back to this feature when new uImage is in place.
Cheers,
m.