+Tom in case he has a comment
Hi Karl,
On 15 May 2015 at 15:13, Karl Apsite <karl.aps...@dornerworks.com> wrote:
>
> The FIT config now supports a tag named "loadables:" which is a
> comma separated list. Users can add any number of images to the list,
> and u-boot will move the selected binaries to their listed
> load_addresses. This allows u-boot to boot xen from using an FIT
> configuration. Xen expects a kernel to be placed at a predetermined
> location, however the "kernel" field was already filled by xen itself.
> This change allows the user to move the required binary before xen
> boots, all within the FIT's configuration.
>
I think I've convinced myself that this ('loadables') is a good
solution to the problem. I'm not 100% comfortable with the name but I
don't have a better one, and no one else has chimed in.
Will you actually use multiple images in your application?
>
> Karl Apsite (4):
> add test for two 'loadables'
> mkimage will now report information about loadable
> add boot_get_loadables() to load listed images
> Combine bootm_find_<thing> functions together
>
> common/bootm.c | 49 ++++++++++++-----------
> common/cmd_bootm.c | 4 +-
> common/image-fit.c | 25 +++++++++++-
> common/image.c | 71 ++++++++++++++++++++++++++++++++++
> doc/uImage.FIT/source_file_format.txt | 4 ++
> include/bootm.h | 2 +-
> include/bootstage.h | 1 +
> include/image.h | 28 +++++++++++++-
> test/image/test-fit.py | 73
> ++++++++++++++++++++++++++++++-----
> 9 files changed, 221 insertions(+), 36 deletions(-)
>
> --
> 2.3.7
>
Regards,
Simon
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
