u-boot.git/doc/uImage.FIT, branch v2016.07 Unnamed repository; edit this file 'description' to name the repository. mkimage: fit: spl: Add an optional static offset for external data 2016-06-24T21:23:06+00:00 Teddy Reed teddy.reed@gmail.com 2016-06-10T02:38:02+00:00 f8f9107d97b849afe69ca86e7abd8d1748ea7acd When building a FIT with external data (-E), U-Boot proper may require absolute positioning for executing the external firmware. To acheive this use the (-p) switch, which will replace the amended 'data-offset' with 'data-position' indicating the absolute position of external data. It is considered an error if the requested absolute position overlaps with the initial data required for the compact FIT. Signed-off-by: Teddy Reed <teddy.reed@gmail.com> 
When building a FIT with external data (-E), U-Boot proper may require
absolute positioning for executing the external firmware. To acheive this
use the (-p) switch, which will replace the amended 'data-offset' with
'data-position' indicating the absolute position of external data.

It is considered an error if the requested absolute position overlaps with the
initial data required for the compact FIT.

Signed-off-by: Teddy Reed <teddy.reed@gmail.com>
mkimage: Report information about fpga 2016-05-24T09:15:02+00:00 Michal Simek michal.simek@xilinx.com 2016-05-17T11:58:44+00:00 ed0cea7c5271cbfd37089f3a6392ba383eda06f7 Add FIT_FPGA_PROP that user can identify an optional entry for fpga. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Add FIT_FPGA_PROP that user can identify an optional
entry for fpga.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
doc: clarify openssl-based key and certificate generation process 2016-04-01T21:17:41+00:00 Andreas Dannenberg dannenberg@ti.com 2016-03-23T23:24:10+00:00 4c1d5c29b5dec31f838dbe860ea682debaf27efe Add some basic clarification that the dev.key file generated by OpenSSL contains both the public and private key, and further highlight that the certificate generated here contains the public key only. Signed-off-by: Andreas Dannenberg <dannenberg@ti.com> 
Add some basic clarification that the dev.key file generated by OpenSSL
contains both the public and private key, and further highlight that
the certificate generated here contains the public key only.

Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
doc: fix file extension for flattened image tree blob 2016-04-01T21:17:41+00:00 Andreas Dannenberg dannenberg@ti.com 2016-03-23T22:44:17+00:00 486c39c2e956939125a4a25fbd644b2b620a103d Different sections in the document suggest flattened image tree blob files have a file name extension of .itb. Fix the list of file extensions to reflect that. Signed-off-by: Andreas Dannenberg <dannenberg@ti.com> 
Different sections in the document suggest flattened image tree blob
files have a file name extension of .itb. Fix the list of file extensions
to reflect that.

Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
mkimage: Support placing data outside the FIT 2016-03-14T23:18:29+00:00 Simon Glass sjg@chromium.org 2016-02-23T05:55:53+00:00 722ebc8f84d5bccd2e70fad1079a0dd40cceddec 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> 
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>
Use correct spelling of "U-Boot" 2016-02-06T11:00:59+00:00 Bin Meng bmeng.cn@gmail.com 2016-02-06T03:30:11+00:00 a187559e3d586891c917279044c5386d1b2adc6e Correct spelling of "U-Boot" shall be used in all written text (documentation, comments in source files etc.). Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Heiko Schocher <hs@denx.de> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Minkyu Kang <mk7.kang@samsung.com> 
Correct spelling of "U-Boot" shall be used in all written text
(documentation, comments in source files etc.).

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Heiko Schocher <hs@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Minkyu Kang <mk7.kang@samsung.com>
mkimage will now report information about loadable 2015-05-28T12:18:20+00:00 Karl Apsite karl.apsite@dornerworks.com 2015-05-21T13:52:47+00:00 ecf8cd653530acb0ed8217a1d80c93841ec2005e Added FIT_LOADABLE_PROP, so the user can identify an optional entry named "loadables" in their .its configuration. "loadables" is a comma separated list in the .its Documentation can be found in doc/uImage.FIT/source_file_format.txt and doc/uImage.Fit/multi-with-loadables.its Signed-off-by: Karl Apsite <Karl.Apsite@dornerworks.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Added FIT_LOADABLE_PROP, so the user can identify an optional entry
named "loadables" in their .its configuration. "loadables" is a comma
separated list in the .its

Documentation can be found in doc/uImage.FIT/source_file_format.txt and
                              doc/uImage.Fit/multi-with-loadables.its

Signed-off-by: Karl Apsite <Karl.Apsite@dornerworks.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
doc: fix misspellings 2015-01-29T18:38:40+00:00 Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com 2015-01-15T04:37:34+00:00 a724b7e0ab28d7b6a2aed1a0b7d46b0e662c2372 Signed-off-by: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com> 
Signed-off-by: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
doc: "os" is also mandatory for "ramdisk" FIT image components 2015-01-29T18:38:40+00:00 Guilherme Maciel Ferreira guilherme.maciel.ferreira@gmail.com 2015-01-15T04:37:33+00:00 5cde9d8e94de759cacf99b08dd373cb18768feba According to fit_image_print(), the "os" property from "image" node is required also when "type=ramdisk". Signed-off-by: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com> 
According to fit_image_print(), the "os" property from "image" node is required
also when "type=ramdisk".

Signed-off-by: Guilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
x86: Support loading kernel setup from a FIT 2014-10-22T15:03:06+00:00 Simon Glass sjg@chromium.org 2014-10-20T03:11:24+00:00 90268b878bd830f2fc9b1e225d96009efe331cd1 Add a new setup@ section to the FIT which can be used to provide a setup binary for booting Linux on x86. This makes it possible to boot x86 from a FIT. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a new setup@ section to the FIT which can be used to provide a setup
binary for booting Linux on x86. This makes it possible to boot x86 from
a FIT.

Signed-off-by: Simon Glass <sjg@chromium.org>