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, v2018.07 |
|
#
83d290c5 |
| 06-May-2018 |
Tom Rini <trini@konsulko.com> |
SPDX: Convert all of our single license tags to Linux Kernel style
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So
SPDX: Convert all of our single license tags to Linux Kernel style
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us.
In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style.
This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one.
Signed-off-by: Tom Rini <trini@konsulko.com>
show more ...
|
Revision tags: v2018.03 |
|
#
94b13bba |
| 21-Jan-2018 |
Masahiro Yamada <yamada.masahiro@socionext.com> |
host-tools: use python2 explicitly for shebang
All of these host tools are apparently written for Python2, not Python3.
Use 'python2' in the shebang line according to PEP 394 (https://www.python.or
host-tools: use python2 explicitly for shebang
All of these host tools are apparently written for Python2, not Python3.
Use 'python2' in the shebang line according to PEP 394 (https://www.python.org/dev/peps/pep-0394/).
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
Revision tags: v2018.01 |
|
#
bb7ab1cc |
| 23-Nov-2017 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
Revision tags: v2017.11 |
|
#
cb39a109 |
| 12-Nov-2017 |
Simon Glass <sjg@chromium.org> |
buildman: Allow skipping of tests which use the network
Accessing the network slows down the test and limits the environment in which it can be run. Add an option to disable network tests.
Signed-o
buildman: Allow skipping of tests which use the network
Accessing the network slows down the test and limits the environment in which it can be run. Add an option to disable network tests.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
79493609 |
| 12-Oct-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
a556eeeb |
| 18-Sep-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Put our local libraries first in the path
If patman is installed on the machine (e.g. in the standard dist-packages directory), it will find libraries from there in preference to our local
buildman: Put our local libraries first in the path
If patman is installed on the machine (e.g. in the standard dist-packages directory), it will find libraries from there in preference to our local libraries. Adjust the order of the path to ensure that local libraries are found first.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
Revision tags: v2016.07, openbmc-20160624-1, v2016.01-rc1, v2015.10, v2015.10-rc5, v2015.10-rc4, v2015.10-rc3, v2015.10-rc2, v2015.10-rc1, v2015.07, v2015.07-rc3, v2015.07-rc2, v2015.07-rc1, v2015.04, v2015.04-rc5, v2015.04-rc4, v2015.04-rc3, v2015.04-rc2, v2015.04-rc1, v2015.01, v2015.01-rc4, v2015.01-rc3, v2015.01-rc2, v2015.01-rc1, v2014.10, v2014.10-rc3 |
|
#
42817eb8 |
| 22-Sep-2014 |
Stefano Babic <sbabic@denx.de> |
Merge branch 'master' of git://git.denx.de/u-boot-arm
|
#
5935408a |
| 09-Sep-2014 |
Tom Rini <trini@ti.com> |
Merge branch 'buildman' of git://git.denx.de/u-boot-x86
|
#
fd03d63f |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Set up bsettings outside the control module
Move the bsettings code back to the main buildman.py file, so we can do something different when testing.
Signed-off-by: Simon Glass <sjg@chrom
buildman: Set up bsettings outside the control module
Move the bsettings code back to the main buildman.py file, so we can do something different when testing.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
d4144e45 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add a functional test
Buildman currently lacks testing in many areas, including its use of git, make and many command-line flags.
Add a functional test which covers some of these areas. S
buildman: Add a functional test
Buildman currently lacks testing in many areas, including its use of git, make and many command-line flags.
Add a functional test which covers some of these areas. So far it does a fake 'build' of all boards for the current source tree.
This version reads the real ~/.buildman and boards.cfg files. Future work will improve this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
48ba5856 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Move full help code into the control module
There is no good reason to keep this code separate. Move it into control.py so it is easier to test.
Signed-off-by: Simon Glass <sjg@chromium.o
buildman: Move full help code into the control module
There is no good reason to keep this code separate. Move it into control.py so it is easier to test.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
d3d5c123 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Move the command line code into its own file
We want to be able to issue parser commands from within buildman for test purposes. Move the parser code into its own file so we don't end up n
buildman: Move the command line code into its own file
We want to be able to issue parser commands from within buildman for test purposes. Move the parser code into its own file so we don't end up needing the buildman and test modules to reference each other.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
Revision tags: v2014.10-rc2 |
|
#
ed966657 |
| 28-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to show which boards caused which errors
Add a -l option to display a list of offending boards against each error/warning line. The information will be shown in brackets as b
buildman: Add an option to show which boards caused which errors
Add a -l option to display a list of offending boards against each error/warning line. The information will be shown in brackets as below:
02: wip sandbox: + sandbox arm: + seaboard +(sandbox) arch/sandbox/cpu/cpu.c: In function 'timer_get_us': +(sandbox) arch/sandbox/cpu/cpu.c:40:9: warning: unused variable 'i' [-Wunused-variable] +(seaboard) board/nvidia/seaboard/seaboard.c: In function 'pin_mux_mmc': +(seaboard) board/nvidia/seaboard/seaboard.c:36:9: warning: unused variable 'fred' [-Wunused-variable] +(seaboard) int fred; +(seaboard) ^
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
3cf4ae6f |
| 28-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Implement an option to exclude boards from the build
Some boards are known to be broken and it is convenient to be able to exclude them from the build.
Add an --exclude option to specific
buildman: Implement an option to exclude boards from the build
Some boards are known to be broken and it is convenient to be able to exclude them from the build.
Add an --exclude option to specific boards to exclude. This uses the same matching rules as the normal 'include' arguments, and is a comma- separated list of regular expressions.
Suggested-by: York Sun <yorksun@freescale.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
2c3deb97 |
| 28-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Set the return code to indicate build result
When buildman finds errors/warnings when building, set the return code to indicate this.
Suggested-by: York Sun <yorksun@freescale.com> Signed
buildman: Set the return code to indicate build result
When buildman finds errors/warnings when building, set the return code to indicate this.
Suggested-by: York Sun <yorksun@freescale.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
7f6b8315 |
| 22-Aug-2014 |
Masahiro Yamada <yamada.m@jp.panasonic.com> |
buildman: refactor help message
"buildman [options]" is displayed by default.
Append the rest of help messages to parser.usage instead of replacing it.
Besides, "-b <branch>" is not mandatory sinc
buildman: refactor help message
"buildman [options]" is displayed by default.
Append the rest of help messages to parser.usage instead of replacing it.
Besides, "-b <branch>" is not mandatory since commit fea5858e. Drop it from the usage.
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
show more ...
|
#
0f7c9dda |
| 09-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add an option to specify the buildman config file
Add a new --config-file option (-G) to specify a different configuration file from the default ~/.buildman.
Reported-by: Tom Rini <trini@
buildman: Add an option to specify the buildman config file
Add a new --config-file option (-G) to specify a different configuration file from the default ~/.buildman.
Reported-by: Tom Rini <trini@ti.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
e5a0e5d8 |
| 09-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add verbose option to display errors as they happen
Normally buildman operates in two passes - one to do the build and another to summarise the errors. Add a verbose option (-v) to display
buildman: Add verbose option to display errors as they happen
Normally buildman operates in two passes - one to do the build and another to summarise the errors. Add a verbose option (-v) to display build problems as they happen. With -e also given, this will display errors too.
When building the current source tree (rather than a list of commits in a branch), both -v and -e are enabled automatically.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
c1de5014 |
| 09-Aug-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Sort command line options
These options have got slightly out of order. Fix them.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
e82abaeb |
| 11-Aug-2014 |
Stefano Babic <sbabic@denx.de> |
Merge branch 'master' of git://git.denx.de/u-boot-arm
Conflicts: boards.cfg
Signed-off-by: Stefano Babic <sbabic@denx.de>
|
#
c23154aa |
| 08-Aug-2014 |
Stefano Babic <sbabic@denx.de> |
Merge branch 'master' of git://git.denx.de/u-boot-arm
|
Revision tags: v2014.10-rc1 |
|
#
189a4968 |
| 14-Jul-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Support in-tree builds
At present buildman always builds out-of-tree, that is it uses a separate output directory from the source directory. Normally this is what you want, but it is impor
buildman: Support in-tree builds
At present buildman always builds out-of-tree, that is it uses a separate output directory from the source directory. Normally this is what you want, but it is important that in-tree builds work also. Some Makefile changes may break this.
Add a -i option to tell buildman to use in-tree builds, so that it is easy to test this feature.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
97e91526 |
| 14-Jul-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add -C option to force a reconfigure for each commit
Normally buildman wil try to configure U-Boot for a particular board on the first commit that it builds in a series. Subsequent commits
buildman: Add -C option to force a reconfigure for each commit
Normally buildman wil try to configure U-Boot for a particular board on the first commit that it builds in a series. Subsequent commits are built without reconfiguring which normally works. Where it doesn't, buildman automatically reconfigures and retries.
To fully emulate the way MAKEALL works, we should have an option to disable this optimisation.
Add a -C option to cause buildman to always reconfigure on each commit.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
Revision tags: v2014.07 |
|
#
4266dc28 |
| 13-Jul-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add -F flag to retry failed builds
Generally a build failure with a particular commit cannot be fixed except by changing that commit. Changing the commit will automatically cause buildman
buildman: Add -F flag to retry failed builds
Generally a build failure with a particular commit cannot be fixed except by changing that commit. Changing the commit will automatically cause buildman to retry when you run it again: buildman sees that the commit hash is different and that it has no previous build result for the new commit hash.
However sometimes the build failure is due to a toolchain issue or some other environment problem. In that case, retrying failed builds may yield a different result.
Add a flag to retry failed builds. This differs from the force rebuild flag (-f) in that it will not rebuild commits which are already marked as succeeded.
Series-to: u-boot
Change-Id: Iac4306df499d65ff0888b1c60f06fc162a6faad8
show more ...
|
Revision tags: v2014.07-rc4, v2014.07-rc3, v2014.07-rc2 |
|
#
e7f93505 |
| 15-May-2014 |
Stefano Babic <sbabic@denx.de> |
Merge branch 'master' of git://git.denx.de/u-boot-arm
|