u-boot.git/tools, branch v2020.01-rc2 Unnamed repository; edit this file 'description' to name the repository. binman: tegra: Adjust symbol calculation depending on end-at-4gb 2019-11-11T19:20:35+00:00 Simon Glass sjg@chromium.org 2019-11-07T00:22:44+00:00 7c150136398916ac546b5a902d09208cc793cabe A recent change adjusted the symbol calculation to work on x86 but broke it for Tegra. In fact this is because they have different needs. On x86 devices the code is linked to a ROM address and the end-at-4gb property is used for the image. In this case there is no need to add the base address of the image, since the base address is already built into the offset and image-pos properties. On other devices we must add the base address since the offsets start at zero. In addition the base address is currently added to the 'offset' and 'size' values. It should in fact only be added to 'image-pos', since 'offset' is relative to its parent and 'size' is not actually an address. This code should have been adjusted when support for 'image-pos' and 'size' was added, but it was not. To correct these problems: - move the code that handles adding the base address to section.py, which can check the end-at-4gb property and which property (offset/size/image-pos) is being read - add the base address only when needed (only for image-pos and not if the image uses end-at-4gb) - add a note to the documentation - add a separate test to cover x86 behaviour Fixes: 15c981cc (binman: Correct symbol calculation with non-zero image base) Signed-off-by: Simon Glass <sjg@chromium.org> Tested-by: Stephen Warren <swarren@nvidia.com> 
A recent change adjusted the symbol calculation to work on x86 but broke
it for Tegra. In fact this is because they have different needs.

On x86 devices the code is linked to a ROM address and the end-at-4gb
property is used for the image. In this case there is no need to add the
base address of the image, since the base address is already built into
the offset and image-pos properties.

On other devices we must add the base address since the offsets start at
zero.

In addition the base address is currently added to the 'offset' and 'size'
values. It should in fact only be added to 'image-pos', since 'offset' is
relative to its parent and 'size' is not actually an address. This code
should have been adjusted when support for 'image-pos' and 'size' was
added, but it was not.

To correct these problems:
- move the code that handles adding the base address to section.py, which
  can check the end-at-4gb property and which property
  (offset/size/image-pos) is being read
- add the base address only when needed (only for image-pos and not if the
  image uses end-at-4gb)
- add a note to the documentation
- add a separate test to cover x86 behaviour

Fixes: 15c981cc (binman: Correct symbol calculation with non-zero image base)

Signed-off-by: Simon Glass <sjg@chromium.org>
Tested-by: Stephen Warren <swarren@nvidia.com>
tools/img2brec.sh: Delete unused tool 2019-11-08T19:04:53+00:00 Tom Rini trini@konsulko.com 2019-11-08T14:26:18+00:00 fb6dc1fd58fc3209f833ddcd155fe1b276e7a335 This script was only used on the MX1ADS board (and possibly other MX1 platforms) to program the flash. As we no longer have any boards for that SoC, remove this tool. Fixes: e570aca9474b ("mx1ads: remove board support") Signed-off-by: Tom Rini <trini@konsulko.com> 
This script was only used on the MX1ADS board (and possibly other MX1
platforms) to program the flash.  As we no longer have any boards for
that SoC, remove this tool.

Fixes: e570aca9474b ("mx1ads: remove board support")
Signed-off-by: Tom Rini <trini@konsulko.com>
binman: Move to use Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:43:05+00:00 388560134b99dc4cc752627d3a7e9f8c8c2a89a7 Update this tool to use Python 3 to meet the 2020 deadline. Unfortunately this introduces a test failure due to a problem in pylibfdt on Python 3. I will investigate. Signed-off-by: Simon Glass <sjg@chromium.org> 
Update this tool to use Python 3 to meet the 2020 deadline.

Unfortunately this introduces a test failure due to a problem in pylibfdt
on Python 3. I will investigate.

Signed-off-by: Simon Glass <sjg@chromium.org>
dtoc: Convert fdt.py to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:43:04+00:00 a90df2b17282c43600284a92bf034d81d0c49444 Drop the now-unused Python 2 code to keep code coverage at 100%. Signed-off-by: Simon Glass <sjg@chromium.org> 
Drop the now-unused Python 2 code to keep code coverage at 100%.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Convert a few tests to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:43:03+00:00 b6ee0cf89f9405094cbb6047076a13e14ebc030b Some tests have crept in with Python 2 strings and constructs. Convert then. Signed-off-by: Simon Glass <sjg@chromium.org> 
Some tests have crept in with Python 2 strings and constructs. Convert
then.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Remember the pre-reset entry size 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:43:02+00:00 9a5d3dcff7894a24e493e6ae52d289d190d3ccdf When preparing to possible expand or contract an entry we reset the size to the original value from the binman device-tree definition, which is often None. This causes binman to forget the original size of the entry. Remember this so that it can be used when needed. Signed-off-by: Simon Glass <sjg@chromium.org> 
When preparing to possible expand or contract an entry we reset the size
to the original value from the binman device-tree definition, which is
often None.

This causes binman to forget the original size of the entry. Remember this
so that it can be used when needed.

Signed-off-by: Simon Glass <sjg@chromium.org>
pylibfdt: Convert to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:42:59+00:00 b4cf5f1df741e8781bed6149291823cd1a4b8baa Build this swig module with Python 3. Signed-off-by: Simon Glass <sjg@chromium.org> 
Build this swig module with Python 3.

Signed-off-by: Simon Glass <sjg@chromium.org>
rkmux: Convert to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:42:58+00:00 5effab0549da404e0f2c21a3f7585aa643f54fc8 Convert this tool to Python 3 and make it use that, to meet the 2020 deadline. Signed-off-by: Simon Glass <sjg@chromium.org> 
Convert this tool to Python 3 and make it use that, to meet the 2020
deadline.

Signed-off-by: Simon Glass <sjg@chromium.org>
move_config: Convert to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:42:57+00:00 793dca34ca02716d4045fb232fd0854df1c46888 Convert this tool to Python 3 and make it use that, to meet the 2020 deadline. Signed-off-by: Simon Glass <sjg@chromium.org> 
Convert this tool to Python 3 and make it use that, to meet the 2020
deadline.

Signed-off-by: Simon Glass <sjg@chromium.org>
microcode_tool: Convert to Python 3 2019-11-05T01:15:32+00:00 Simon Glass sjg@chromium.org 2019-10-31T13:42:56+00:00 879ca276567fefa272ca2a4c45cedc179e17857e Convert this tool to Python 3 and make it use that, to meet the 2020 deadline. Signed-off-by: Simon Glass <sjg@chromium.org> 
Convert this tool to Python 3 and make it use that, to meet the 2020
deadline.

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