Revision tags: v00.04.15, v00.04.14, v00.04.13, v00.04.12, v00.04.11, v00.04.10, v00.04.09, v00.04.08, v00.04.07, v00.04.06, v00.04.05, v00.04.04, v00.04.03, v00.04.02, v00.04.01, v00.04.00, v2021.04, v00.03.03, v2021.01, v2020.10, v2020.07, v00.02.13, v2020.04, v2020.01, v2019.10, v00.02.05, v00.02.04, v00.02.03, v00.02.02, v00.02.01, v2019.07, v00.02.00, v2019.04 |
|
#
d24c1d0f |
| 30-Sep-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
f8f8df6e |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Correct fmap output on x86
Normally x86 platforms use the end-at-4gb option. This currently produces an FMAP with positions which have a large offset. The use of end-at-4gb is a useful conve
binman: Correct fmap output on x86
Normally x86 platforms use the end-at-4gb option. This currently produces an FMAP with positions which have a large offset. The use of end-at-4gb is a useful convenience within binman, but we don't really want to export a map with these offsets.
Fix this by subtracting the 'skip at start' parameter.
Also put the code which convers names to fmap format, for clarity.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
08723a7a |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Record the parent section of each section
At present sections have no record of their parent so it is not possible to traverse up the tree to the root and figure out the position of a sectio
binman: Record the parent section of each section
At present sections have no record of their parent so it is not possible to traverse up the tree to the root and figure out the position of a section within the image.
Change the constructor to record this information.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
e0e5df93 |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Support hashing entries
Sometimesi it us useful to be able to verify the content of entries with a hash. Add an easy way to do this in binman. The hash information can be retrieved from the
binman: Support hashing entries
Sometimesi it us useful to be able to verify the content of entries with a hash. Add an easy way to do this in binman. The hash information can be retrieved from the device tree at run time.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
ba64a0bb |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Support expanding entries
It is useful to have entries which can grow automatically to fill available space. Add support for this.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
0a98b28b |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Support adding files
In some cases it is useful to add a group of files to the image and be able to access them at run-time. Of course it is possible to generate the binman config file with
binman: Support adding files
In some cases it is useful to add a group of files to the image and be able to access them at run-time. Of course it is possible to generate the binman config file with a set of blobs each with a filename. But for convenience, add an entry type which can do this.
Add required support (for adding nodes and string properties) into the state module.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
b4e1a38c |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Allow zero-size sections
At present if there is only a zero-size entry in a section this is reported as an error, e.g.:
Offset 0x0 (0) is outside the section starting at 0x0 (0)
Adjust
binman: Allow zero-size sections
At present if there is only a zero-size entry in a section this is reported as an error, e.g.:
Offset 0x0 (0) is outside the section starting at 0x0 (0)
Adjust the logic in CheckEntries() to avoid this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
d29a5831 |
| 29-Sep-2018 |
Tom Rini <trini@konsulko.com> |
Merge tag 'mpc85xx-for-v2018.11-rc1' of git://git.denx.de/u-boot-mpc85xx
Use device tree for mpc85xx with binman. Enabled for T2080QDS.
|
#
539aece5 |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Obtain the list of device trees from the config
We always have a device tree for U-Boot proper. But we may also have one for SPL and TPL. Add a new Entry method to find out what DTs an entry
binman: Obtain the list of device trees from the config
We always have a device tree for U-Boot proper. But we may also have one for SPL and TPL. Add a new Entry method to find out what DTs an entry has, and use that list when updating DTs.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
f46621d2 |
| 14-Sep-2018 |
Simon Glass <sjg@chromium.org> |
binman: Centralise device-tree updates within binman
At present we have a few calls to device-tree functions in binman and plan to add more as we add new entry types which need to report their resul
binman: Centralise device-tree updates within binman
At present we have a few calls to device-tree functions in binman and plan to add more as we add new entry types which need to report their results.
It makes sense to put this code in a central place so that we can make sure all device trees are updated. At present we only have U-Boot proper, but plan to add SPL and TPL too.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
94b57db0 |
| 03-Sep-2018 |
Jagdish Gediya <jagdish.gediya@nxp.com> |
binman: Add a new "skip-at-start" property in Section class
Currently binman calculates '_skip_at_start' based on 'end-at-4gb' property and it is used for x86 images.
For PowerPC mpc85xx based CPU,
binman: Add a new "skip-at-start" property in Section class
Currently binman calculates '_skip_at_start' based on 'end-at-4gb' property and it is used for x86 images.
For PowerPC mpc85xx based CPU, CONFIG_SYS_TEXT_BASE is the entry offset of the first entry. It can be 0xeff40000 or 0xfff40000 for nor flash boot, 0x201000 for sd boot etc, so "_skip_at_start" should be set to CONFIG_SYS_TEXT_BASE.
'end-at-4gb' property is not applicable where CONFIG_SYS_TEXT_BASE + Image size != 4gb.
Add new property 'skip-at-start' in Section class so that '_skip_at_start' can be calculated either based on 'end-at-4gb' or based on "skip-at-start".
Add a test case to check that 'skip-at-start' and 'end-at-4gb' property can't be used together.
Signed-off-by: Jagdish Gediya <jagdish.gediya@nxp.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: York Sun <york.sun@nxp.com>
show more ...
|
#
a30691a5 |
| 03-Aug-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
1be70d20 |
| 17-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Show the image position in the map
At present the map only shows the offset and size for each region. The image position provides the actual position of each entry in the image, regardless o
binman: Show the image position in the map
At present the map only shows the offset and size for each region. The image position provides the actual position of each entry in the image, regardless of the section hierarchy.
Add the image position to the map.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
24d0d3c3 |
| 17-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add an entry for a Chromium vblock
This adds support for a Chromium verified boot block, used to sign a read-write section of the image.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
dbf6be9f |
| 01-Aug-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add a new 'image-pos' property
At present each entry has an offset within its parent section. This is useful for figuring out how entries relate to one another. However it is sometimes neces
binman: Add a new 'image-pos' property
At present each entry has an offset within its parent section. This is useful for figuring out how entries relate to one another. However it is sometimes necessary to locate an entry within an image, regardless of which sections it is nested inside.
Add a new 'image-pos' property to provide this information. Also add some documentation for the -u option binman provides, which updates the device tree with final entry information.
Since the image position is a better symbol to use for the position of U-Boot as obtained by SPL, update the SPL symbols to use this instead of offset, which might be incorrect if hierarchical sections are used.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
8122f396 |
| 17-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Enhance the map and fdt-update output
At present the .map file produced for each image does not include the overall image size. This is useful information.
Update the code to generate it in
binman: Enhance the map and fdt-update output
At present the .map file produced for each image does not include the overall image size. This is useful information.
Update the code to generate it in the .map file as well as the updated FDT. Also fix a few comments while we are here.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
3ab9598d |
| 01-Aug-2018 |
Simon Glass <sjg@chromium.org> |
binman: Rename 'position' to 'offset'
After some thought, I believe there is an unfortunate naming flaw in binman. Entries have a position and size, but now that we support hierarchical sections it
binman: Rename 'position' to 'offset'
After some thought, I believe there is an unfortunate naming flaw in binman. Entries have a position and size, but now that we support hierarchical sections it is unclear whether a position should be an absolute position within the image, or a relative position within its parent section.
At present 'position' actually means the relative position. This indicates a need for an 'image position' for code that wants to find the location of an entry without having to do calculations back through parents to discover this image position.
A better name for the current 'position' or 'pos' is 'offset'. It is not always an absolute position, but it is always an offset from its parent offset.
It is unfortunate to rename this concept now, 18 months after binman was introduced. However I believe it is the right thing to do. The impact is mostly limited to binman itself and a few changes to in-tree users to binman:
tegra sunxi x86
The change makes old binman definitions (e.g. downstream or out-of-tree) incompatible if they use the 'pos = <...>' property. Later work will adjust binman to generate an error when it is used.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
e3396ffd |
| 10-Jul-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
Revision tags: v2018.07 |
|
#
078ab1a2 |
| 06-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add a SetCalculatedProperties() method
Once binman has packed the image, the position and size of each entry is known. It is then possible for binman to update the device tree with these pos
binman: Add a SetCalculatedProperties() method
Once binman has packed the image, the position and size of each entry is known. It is then possible for binman to update the device tree with these positions. Since placeholder values have been added, this does not affect the size of the device tree and therefore the packing does not need to be performed again.
Add a new SetCalculatedProperties method to handle this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
ecab8973 |
| 06-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add a ProcessFdt() method
Some entry types modify the device tree, e.g. to remove microcode or add a property. So far this just modifies their local copy and does not affect a 'shared' devic
binman: Add a ProcessFdt() method
Some entry types modify the device tree, e.g. to remove microcode or add a property. So far this just modifies their local copy and does not affect a 'shared' device tree.
Rather than doing this modification in the ObtainContents() method, and a new ProcessFdt() method which is specifically designed to modify this shared device tree.
Move the existing device-tree code over to use this method, reducing ObtainContents() to the goal of just obtaining the contents without any processing, even for device tree.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
736bb0ae |
| 06-Jul-2018 |
Simon Glass <sjg@chromium.org> |
binman: Correct operation of ObtainContents()
This method is supposed to return the contents of an entry. However at present there is no check that it actually does. Also some implementations do not
binman: Correct operation of ObtainContents()
This method is supposed to return the contents of an entry. However at present there is no check that it actually does. Also some implementations do not return 'True' to indicate success, as required.
Add a check for things working as expected, and correct the implementations.
This requires some additional test cases to cover things which were missed originally. Add these at the same time.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
8f48cf9f |
| 08-Jun-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
c8d48efb |
| 01-Jun-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add support for adding a name prefix to entries
Sometimes we have several sections which repeat the same entries (e.g. for a read-only and read-write version of the same section). It is usef
binman: Add support for adding a name prefix to entries
Sometimes we have several sections which repeat the same entries (e.g. for a read-only and read-write version of the same section). It is useful to be able to tell these entries apart by name.
Add a new 'name-prefix' property for sections, which causes all entries within that section to have a given name prefix.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
3b0c3821 |
| 01-Jun-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add support for outputing a map file
It is useful to be able to see a list of regions in each image produced by binman. Add a -m option to output this information in a '.map' file alongside
binman: Add support for outputing a map file
It is useful to be able to see a list of regions in each image produced by binman. Add a -m option to output this information in a '.map' file alongside the image file.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
1854695b |
| 01-Jun-2018 |
Simon Glass <sjg@chromium.org> |
binman: Add support for sections
It is useful to be able to split an image into multiple sections, each with its own size and position, for cases where a flash device has read-only and read-write po
binman: Add support for sections
It is useful to be able to split an image into multiple sections, each with its own size and position, for cases where a flash device has read-only and read-write portions.
Add support for this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|