| 529fd188 | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Bring data into the FIT before processing
Since we now support data outside the FIT image, bring it into the FIT image first before we do any processing. This avoids adding new functionalit
mkimage: Bring data into the FIT before processing
Since we now support data outside the FIT image, bring it into the FIT image first before we do any processing. This avoids adding new functionality to the core FIT code for now.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 722ebc8f | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Support placing data outside the FIT
One limitation of FIT is that all the data is 'inline' within it, using a 'data' property in each image node. This means that to find out what is in the
mkimage: Support placing data outside the FIT
One limitation of FIT is that all the data is 'inline' within it, using a 'data' property in each image node. This means that to find out what is in the FIT it is necessary to scan the entire file. Once loaded it can be scanned and then the images can be copied to the correct place in memory.
In SPL it can take a significant amount of time to copy images around in memory. Also loading data that does not end up being used is wasteful. It would be useful if the FIT were small, acting as a directory, with the actual data stored elsewhere.
This allows SPL to load the entire FIT, without the images, then load the images it wants later.
Add a -E option to mkimage to request that it output an 'external' FIT.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| fb4cce0f | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Support adding device tree files to a FIT
To make the auto-FIT feature useful we need to be able to provide a list of device tree files on the command line for mkimage to add into the FIT.
mkimage: Support adding device tree files to a FIT
To make the auto-FIT feature useful we need to be able to provide a list of device tree files on the command line for mkimage to add into the FIT. Add support for this feature.
So far there is no support for hashing or verified boot using this method. For those cases, a .its file must still be provided.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 8e35bb07 | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Support automatic creating of a FIT without a .its
At present, when generating a FIT, mkimage requires a .its file containing the structure of the FIT and referring to the images to be incl
mkimage: Support automatic creating of a FIT without a .its
At present, when generating a FIT, mkimage requires a .its file containing the structure of the FIT and referring to the images to be included.
Creating the .its file is a separate step that makes it harder to use FIT. This is not required for creating legacy images.
Often the FIT is pretty standard, consisting of an OS image, some device tree files and a single configuration. We can handle this case automatically and avoid needing a .its file at all.
To start with, support automatically generate the FIT using a new '-f auto' option. Initially this only supports adding a single image (e.g. a linux kernel) and a single configuration.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| d505a09c | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Allow a FIT to include an image of any type
At present FIT images are set up by providing a device tree source file which is a file with a .its extension. We want to support automatically c
mkimage: Allow a FIT to include an image of any type
At present FIT images are set up by providing a device tree source file which is a file with a .its extension. We want to support automatically creating this file based on the image supplied to mkimage. This means that even though the final file type is always IH_TYPE_FLATDT, the image inside may be something else.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 608e399f | 07-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Allow the toolchain architecture to be specified
At present the architecture is deduced from the toolchain filename. Allow it to be specified by the caller.
Signed-off-by: Simon Glass <sj
buildman: Allow the toolchain architecture to be specified
At present the architecture is deduced from the toolchain filename. Allow it to be specified by the caller.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com
show more ...
|
| ff690df9 | 07-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Allow the toolchain priority to be specified
At present the priority of a toolchain is calculated from its filename based on hard-coded rules. Allow it to be specified by the caller. We wi
buildman: Allow the toolchain priority to be specified
At present the priority of a toolchain is calculated from its filename based on hard-coded rules. Allow it to be specified by the caller. We will use this in a later patch. Also display the priority and provide a message when it is overriden by another toolchain of higher priority.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| ad24ebac | 07-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Fix up a few code inconsistencies in toolchain.py
Normally we use a single quote for strings unless there is a reason not to (such as an embedded single quote). Fix a few counter-examples
buildman: Fix up a few code inconsistencies in toolchain.py
Normally we use a single quote for strings unless there is a reason not to (such as an embedded single quote). Fix a few counter-examples in this file. Also add a missing function-argument comment.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| 2bdeade0 | 07-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: patman: Fix -H when installed as a symlink
It is convenient to install symlinks to buildman and patman in the search patch, such as /usr/local/bin. But when this is done, the -H option fai
buildman: patman: Fix -H when installed as a symlink
It is convenient to install symlinks to buildman and patman in the search patch, such as /usr/local/bin. But when this is done, the -H option fails to work because it looks in the directory containing the symlink instead of its target. Fix this.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
| 15310348 | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Show an error message when usage() is called
Sometimes incorrect arguments are supplied but the reason is not obvious to the user. Add some helpful messages.
Signed-off-by: Simon Glass <sj
mkimage: Show an error message when usage() is called
Sometimes incorrect arguments are supplied but the reason is not obvious to the user. Add some helpful messages.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| 07450081 | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Sort the option processing code by option
Adjust the code so that option alphabetical order matches the order in the switch() statement. This makes it easier to find options.
Signed-off-by
mkimage: Sort the option processing code by option
Adjust the code so that option alphabetical order matches the order in the switch() statement. This makes it easier to find options.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| a02221f2 | 23-Feb-2016 |
Simon Glass <sjg@chromium.org> |
mkimage: Convert to use getopt()
The current way of parsing arguments is a bit clumsy. It seems better to use getopt() which is commonly used for this purpose.
Convert the code to use getopt() and
mkimage: Convert to use getopt()
The current way of parsing arguments is a bit clumsy. It seems better to use getopt() which is commonly used for this purpose.
Convert the code to use getopt() and make a few minor adjustments as needed.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| c6e3e821 | 16-Feb-2016 |
Andreas Bießmann <andreas.devel@googlemail.com> |
tools: -Wno-deprecated-declarations for OpenSSL on darwin
Since OpenSSL is deprecated on OS X in favour of Common Crypto API disable the warning for this host OS.
Another solution would be to add s
tools: -Wno-deprecated-declarations for OpenSSL on darwin
Since OpenSSL is deprecated on OS X in favour of Common Crypto API disable the warning for this host OS.
Another solution would be to add some glue layer for crypto stuff, but I think this is not worth the effort.
Signed-off-by: Andreas Bießmann <andreas.devel@googlemail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|