<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/mkimage.c, branch v2016.05-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/mkimage.c?h=v2016.05-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/mkimage.c?h=v2016.05-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2016-03-14T23:18:29Z</updated>
<entry>
<title>mkimage: Support placing data outside the FIT</title>
<updated>2016-03-14T23:18:29Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:53Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=722ebc8f84d5bccd2e70fad1079a0dd40cceddec'/>
<id>urn:sha1:722ebc8f84d5bccd2e70fad1079a0dd40cceddec</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Support adding device tree files to a FIT</title>
<updated>2016-03-14T23:18:29Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fb4cce0f98ea0784130ff544d7c85d0841bea2e6'/>
<id>urn:sha1:fb4cce0f98ea0784130ff544d7c85d0841bea2e6</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Support automatic creating of a FIT without a .its</title>
<updated>2016-03-14T23:18:28Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8e35bb07eb68e524804f2ef53dd18c7cec0b06fc'/>
<id>urn:sha1:8e35bb07eb68e524804f2ef53dd18c7cec0b06fc</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Allow a FIT to include an image of any type</title>
<updated>2016-03-14T23:18:27Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d505a09c1e8fa512aeb3c077048d521f1be302ff'/>
<id>urn:sha1:d505a09c1e8fa512aeb3c077048d521f1be302ff</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Make 'params' static</title>
<updated>2016-03-14T18:19:11Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=cc7a64447bc3e90a8133b2fce98d7526089a7033'/>
<id>urn:sha1:cc7a64447bc3e90a8133b2fce98d7526089a7033</id>
<content type='text'>
This is not used outside mkimage.c, so make this variable static.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Show an error message when usage() is called</title>
<updated>2016-03-14T18:19:11Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1531034831b3098634b524b7e244f577fae21312'/>
<id>urn:sha1:1531034831b3098634b524b7e244f577fae21312</id>
<content type='text'>
Sometimes incorrect arguments are supplied but the reason is not obvious to
the user. Add some helpful messages.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Move usage() up to the top</title>
<updated>2016-03-14T18:19:11Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b0a487a4eb6c1e2214022f927cb3229f2323db44'/>
<id>urn:sha1:b0a487a4eb6c1e2214022f927cb3229f2323db44</id>
<content type='text'>
To avoid a forward declaration, move the usage() function higher in the
file.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Sort the option processing code by option</title>
<updated>2016-03-14T18:19:10Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:35Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0745008145e0a30db06b21533512893ba0f706a2'/>
<id>urn:sha1:0745008145e0a30db06b21533512893ba0f706a2</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Convert to use getopt()</title>
<updated>2016-03-14T18:19:07Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a02221f29deb88145f6a1494450a8b9d20c9d596'/>
<id>urn:sha1:a02221f29deb88145f6a1494450a8b9d20c9d596</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Move argument processing into its own function</title>
<updated>2016-03-14T18:19:01Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-02-23T05:55:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0b443dee6b0a74ac59fdbeda7b5a667c209a5948'/>
<id>urn:sha1:0b443dee6b0a74ac59fdbeda7b5a667c209a5948</id>
<content type='text'>
At present main() is very long. Split out the argument processing to make
it easier to follow.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
