[U-Boot] Please pull u-boot-dm
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
I have had to leave out the live-tree translation patch due to it breaking Jetson-TX1. It looks like you are tracking that:
http://patchwork.ozlabs.org/patch/849881/
It would be good to get that in if we can once we have a respin.
Travis build here (I'm running another now):
https://travis-ci.org/sglass68/u-boot/builds/318440976
The following changes since commit 9da71fc83a38e9dbf71240b3e548f6b37417764a:
Prepare v2018.01-rc2 (2017-12-18 20:55:17 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-dm.git
for you to fetch changes up to a1626e99b5d00f7d99469dc30b6201ab69d4d5bd:
armv8: secure firmware: fix incorrect unit address in node name (2017-12-18 21:25:57 -0700)
---------------------------------------------------------------- Andre Przywara (7): doc: FIT image: fix incorrect description of DT node unit address doc: FIT image: fix incorrect examples of DT node unit address doc: fix incorrect usage of DT node unit address fix incorrect usage of DT node unit address in comments sunxi: arm64: correct usage of DT node address in FIT generation tools: fix incorrect usage of DT node unit address armv8: secure firmware: fix incorrect unit address in node name
Prabhakar Kushwaha (3): common: Fix-up MAC addr in dts by fetching env variable serially arm: Add support of updating dts before fix-up boards: ls1046ardb: disable unavailable "ethernet" node in dts
Simon Glass (6): test: Run binman tests test: Run patman tests test: Run buildman tests test: Run dtoc tests travis.yml: Run tests for tools binman: Run code coverage tests
.travis.yml | 15 ++++ README | 9 ++ .../arm/cpu/armv8/fsl-layerscape/doc/README.falcon | 16 ++-- arch/arm/cpu/armv8/sec_firmware.c | 2 +- arch/arm/lib/bootm-fdt.c | 12 +++ board/freescale/ls1046ardb/eth.c | 51 +++++++++++ board/sunxi/mksunxi_fit_atf.sh | 16 ++-- common/fdt_support.c | 25 +++++- common/image-fit.c | 16 ++-- common/image-sig.c | 2 +- doc/README.uniphier | 36 ++++---- doc/chromium/chromebook_jerry.its | 16 ++-- doc/chromium/nyan-big.its | 16 ++-- doc/uImage.FIT/beaglebone_vboot.txt | 84 ++++++++--------- doc/uImage.FIT/command_syntax_extensions.txt | 42 ++++----- doc/uImage.FIT/howto.txt | 52 +++++------ doc/uImage.FIT/kernel.its | 28 +++--- doc/uImage.FIT/kernel_fdt.its | 20 ++--- doc/uImage.FIT/multi-with-fpga.its | 28 +++--- doc/uImage.FIT/multi-with-loadables.its | 40 ++++----- doc/uImage.FIT/multi.its | 54 +++++------ doc/uImage.FIT/multi_spl.its | 14 +-- doc/uImage.FIT/overlay-fdt-boot.txt | 78 ++++++++-------- doc/uImage.FIT/sign-configs.its | 18 ++-- doc/uImage.FIT/sign-images.its | 16 ++-- doc/uImage.FIT/signature.txt | 100 ++++++++++----------- doc/uImage.FIT/source_file_format.txt | 26 +++--- doc/uImage.FIT/update3.its | 12 +-- doc/uImage.FIT/update_uboot.its | 4 +- doc/uImage.FIT/x86-fit-boot.txt | 10 +-- include/configs/ls1046ardb.h | 2 + include/fdt_support.h | 3 + include/image.h | 26 +++--- test/run | 13 +++ tools/fit_image.c | 24 ++--- tools/image-host.c | 10 +-- 36 files changed, 529 insertions(+), 407 deletions(-)
Regards, Simon
On Tue, Dec 19, 2017 at 06:30:48AM -0700, Simon Glass wrote:
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
The problem is that travis doesn't (yet? I suppose we could add that into the matrix) run 'make tests' but I do. And the new binman tests don't pass, both due to dtc things: 15:56:55 FATAL ERROR: Unrecognized check name "unit_address_vs_reg" and utils: 15:56:58 sh: 1: coverage: not found 15:56:58 Exception: Error running 'coverage report': <type 'str'>
Hi Tom,
On 19 December 2017 at 14:19, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 06:30:48AM -0700, Simon Glass wrote:
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
The problem is that travis doesn't (yet? I suppose we could add that into the matrix) run 'make tests' but I do. And the new binman tests don't pass, both due to dtc things: 15:56:55 FATAL ERROR: Unrecognized check name "unit_address_vs_reg"
That sounds like you need a newer dtc. I wonder if we should run the one in the U-Boot tree?
and utils: 15:56:58 sh: 1: coverage: not found 15:56:58 Exception: Error running 'coverage report': <type 'str'>
Yes you need the coverage tools:
To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
$ sudo apt-get install python-pip python-pytest $ sudo pip install coverage
Regards, Simon
On Tue, Dec 19, 2017 at 02:27:06PM -0700, Simon Glass wrote:
Hi Tom,
On 19 December 2017 at 14:19, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 06:30:48AM -0700, Simon Glass wrote:
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
The problem is that travis doesn't (yet? I suppose we could add that into the matrix) run 'make tests' but I do. And the new binman tests don't pass, both due to dtc things: 15:56:55 FATAL ERROR: Unrecognized check name "unit_address_vs_reg"
That sounds like you need a newer dtc. I wonder if we should run the one in the U-Boot tree?
Yes, not running the one in the U-Boot tree would be a bug :)
and utils: 15:56:58 sh: 1: coverage: not found 15:56:58 Exception: Error running 'coverage report': <type 'str'>
Yes you need the coverage tools:
To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
$ sudo apt-get install python-pip python-pytest $ sudo pip install coverage
Is this documented already somewhere? I can update my docker slaves to include python-coverage.
Hi Tom,
On 19 December 2017 at 14:30, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 02:27:06PM -0700, Simon Glass wrote:
Hi Tom,
On 19 December 2017 at 14:19, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 06:30:48AM -0700, Simon Glass wrote:
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
The problem is that travis doesn't (yet? I suppose we could add that into the matrix) run 'make tests' but I do. And the new binman tests don't pass, both due to dtc things: 15:56:55 FATAL ERROR: Unrecognized check name "unit_address_vs_reg"
That sounds like you need a newer dtc. I wonder if we should run the one in the U-Boot tree?
Yes, not running the one in the U-Boot tree would be a bug :)
Ah OK. Then that means that the coverage patch needs to be dropped / respun.
and utils: 15:56:58 sh: 1: coverage: not found 15:56:58 Exception: Error running 'coverage report': <type 'str'>
Yes you need the coverage tools:
To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
$ sudo apt-get install python-pip python-pytest $ sudo pip install coverage
Is this documented already somewhere? I can update my docker slaves to include python-coverage.
Yes, tools/binman/README
-- Tom
Regards, Simon
participants (2)
-
Simon Glass -
Tom Rini