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 |
|
#
9865543a |
| 06-Aug-2018 |
Masahiro Yamada <yamada.masahiro@socionext.com> |
Remove CONFIG_USE_STDINT
You do not need to use the typedefs provided by compiler.
Our compilers are either IPL32 or LP64. Hence, U-Boot can/should always use int-ll64.h typedefs like Linux kernel
Remove CONFIG_USE_STDINT
You do not need to use the typedefs provided by compiler.
Our compilers are either IPL32 or LP64. Hence, U-Boot can/should always use int-ll64.h typedefs like Linux kernel, whatever the typedefs the compiler internally uses.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
show more ...
|
Revision tags: v2018.07 |
|
#
8f48cf9f |
| 08-Jun-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
0ddc510e |
| 30-May-2018 |
Alex Kiernan <alex.kiernan@gmail.com> |
buildman: Extract environment as part of each build
As we're building the boards, extract the default U-Boot environment to uboot.env so we can interrogate it later.
Signed-off-by: Alex Kiernan <al
buildman: Extract environment as part of each build
As we're building the boards, extract the default U-Boot environment to uboot.env so we can interrogate it later.
Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
00ef2cd6 |
| 16-May-2018 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
#
409fc029 |
| 08-Apr-2018 |
Lothar Waßmann <LW@KARO-electronics.de> |
tools: buildman: Don't use the working dir as build dir
When the U-Boot base directory happens to have the same name as the branch that buildman is directed to use via the '-b' option and no output
tools: buildman: Don't use the working dir as build dir
When the U-Boot base directory happens to have the same name as the branch that buildman is directed to use via the '-b' option and no output directory is specified with '-o', buildman happily starts removing the whole U-Boot sources eventually only stopped with the error message:
OSError: [Errno 20] Not a directory: '../<branch-name>/boards.cfg
Add a check to avoid this and also deal with the case where '-o' points to the source directory, or any subdirectory of it.
Finally, tidy up the confusing logic for removing the old tree when using -b. This is only done when building a branch.
Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de> Signed-off-by: Simon Glass <sjg@chromium.org> Tested-by: Lothar Waßmann <LW@KARO-electronics.de>
show more ...
|
#
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 |
|
#
3759df0c |
| 16-Jan-2018 |
Tom Rini <trini@konsulko.com> |
tools: Update python "help" tests to cope with "more" oddities
In some cases when "more" is told to page a given file it will prepend the output with: :::::::::::::: /PATH/TO/THE/FILE ::::::::::::::
tools: Update python "help" tests to cope with "more" oddities
In some cases when "more" is told to page a given file it will prepend the output with: :::::::::::::: /PATH/TO/THE/FILE ::::::::::::::
And when this happens the output will not match the expected length. Further, if we use a different pager we will instead fail the coverage tests as we will not have 100% coverage. Update the help test to remove the string in question.
Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com>
show more ...
|
Revision tags: v2018.01, v2017.11 |
|
#
b9f7d881 |
| 13-Jun-2017 |
Heiko Schocher <hs@denx.de> |
powerpc, 5xx: remove some "5xx" remains
we removed 5xx support. So delete some forgotten remains.
Signed-off-by: Heiko Schocher <hs@denx.de>
|
#
bd6f5d98 |
| 27-Jul-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Fix the 'help' test to use the correct path
When buildman is run via a symlink, this test fails. Fix it to work the same way as buildman itself.
Signed-off-by: Simon Glass <sjg@chromium.o
buildman: Fix the 'help' test to use the correct path
When buildman is run via a symlink, this test fails. Fix it to work the same way as buildman itself.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
Revision tags: v2016.07, openbmc-20160624-1 |
|
#
d4c8572b |
| 12-Mar-2016 |
Simon Glass <sjg@chromium.org> |
buildman: Allow branch names which conflict with directories
At present if you try to use buildman with the branch 'test' it will complain that it is unsure whether you mean the branch or the direct
buildman: Allow branch names which conflict with directories
At present if you try to use buildman with the branch 'test' it will complain that it is unsure whether you mean the branch or the directory. This is a feature of the 'git log' command that buildman uses. Fix it by resolving the ambiguity.
Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
show more ...
|
Revision tags: 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
|
#
950a2313 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Ignore conflicting tags
Tags like Series-version are normally expected to appear once, and with a unique value. But buildman doesn't actually look at these tags. So ignore conflicts.
This
buildman: Ignore conflicting tags
Tags like Series-version are normally expected to appear once, and with a unique value. But buildman doesn't actually look at these tags. So ignore conflicts.
This allows bulidman to build a branch containing multiple patman series.
Reported-by: Steve Rae <srae@broadcom.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
f7582ce8 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Permit branch names with an embedded '/'
At present buildman naively uses the branch name as part of its directory path, which causes problems if the name has an embedded '/'.
Replace the
buildman: Permit branch names with an embedded '/'
At present buildman naively uses the branch name as part of its directory path, which causes problems if the name has an embedded '/'.
Replace these with '_' to fix the problem.
Reported-by: Steve Rae <srae@broadcom.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
dfb7e932 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Add additional functional tests
This adds coverage of core features of the builder, including the command-line options which affect building.
Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
823e60b6 |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Allow tests to have their own boards
Rather than reading boards.cfg, which may take time to generate and is not necessarily suitable for running tests, create our own list of boards.
Sign
buildman: Allow tests to have their own boards
Rather than reading boards.cfg, which may take time to generate and is not necessarily suitable for running tests, create our own list of boards.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
#
8b985eeb |
| 05-Sep-2014 |
Simon Glass <sjg@chromium.org> |
buildman: Avoid looking at config file or toolchains in tests
These files may not exist in the environment, or may not be suitable for testing. Provide our own config file and our own toolchains whe
buildman: Avoid looking at config file or toolchains in tests
These files may not exist in the environment, or may not be suitable for testing. Provide our own config file and our own toolchains when running tests.
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 ...
|