It is confusing to mention MAKEALL when it is not the normal way of building U-Boot anymore. Update the documentation to suit.
Signed-off-by: Simon Glass sjg@chromium.org ---
README | 35 ++++++----------------------------- board/Barix/ipam390/README.ipam390 | 12 ++++++------ doc/README.sha1 | 5 +++-- 3 files changed, 15 insertions(+), 37 deletions(-)
diff --git a/README b/README index 26d5ad2..704a370 100644 --- a/README +++ b/README @@ -2753,7 +2753,7 @@ CBFS (Coreboot Filesystem) support with a special header) as build targets. By defining CONFIG_BUILD_TARGET in the SoC / board header, this special image will be automatically built upon calling - make / MAKEALL. + make / buildman.
CONFIG_IDENT_STRING
@@ -5078,33 +5078,10 @@ official or latest in the git repository) version of U-Boot sources. But before you submit such a patch, please verify that your modifi- cation did not break existing code. At least make sure that *ALL* of the supported boards compile WITHOUT ANY compiler warnings. To do so, -just run the "MAKEALL" script, which will configure and build U-Boot -for ALL supported system. Be warned, this will take a while. You can -select which (cross) compiler to use by passing a `CROSS_COMPILE' -environment variable to the script, i. e. to use the ELDK cross tools -you can type - - CROSS_COMPILE=ppc_8xx- MAKEALL - -or to build on a native PowerPC system you can type - - CROSS_COMPILE=' ' MAKEALL - -When using the MAKEALL script, the default behaviour is to build -U-Boot in the source directory. This location can be changed by -setting the BUILD_DIR environment variable. Also, for each target -built, the MAKEALL script saves two log files (<target>.ERR and -<target>.MAKEALL) in the <source dir>/LOG directory. This default -location can be changed by setting the MAKEALL_LOGDIR environment -variable. For example: - - export BUILD_DIR=/tmp/build - export MAKEALL_LOGDIR=/tmp/log - CROSS_COMPILE=ppc_8xx- MAKEALL - -With the above settings build objects are saved in the /tmp/build, -log files are saved in the /tmp/log and the source tree remains clean -during the whole build process. +just run the buildman script (tools/buildman/buildman), which will +configure and build U-Boot for ALL supported system. Be warned, this +will take a while. Please see the buildman README, or run 'buildman -H' +for documentation.
See also "U-Boot Porting Guide" below. @@ -6560,7 +6537,7 @@ it:
Notes:
-* Before sending the patch, run the MAKEALL script on your patched +* Before sending the patch, run the buildman script on your patched source tree and make sure that no errors or warnings are reported for any of the boards.
diff --git a/board/Barix/ipam390/README.ipam390 b/board/Barix/ipam390/README.ipam390 index 5c45fca..be09280 100644 --- a/board/Barix/ipam390/README.ipam390 +++ b/board/Barix/ipam390/README.ipam390 @@ -31,9 +31,9 @@ loading the next image from a different media, etc).
Compilation =========== -run "./MAKEALL ipam390" in the u-boot source tree. -Once this build completes you will have a u-boot.ais file that needs to -be written to the nand flash. +run "tools/buildman/buildman -k ipam390" in the u-boot source tree. +Once this build completes you will have a ../current/ipam390/u-boot.ais file +that needs to be written to the nand flash.
Flashing the images to NAND ========================== @@ -71,13 +71,13 @@ here[1] to create an uboot-uart-ais.bin file - cd to the u-boot source tree
- compile the u-boot for the ipam390 board: -$ ./MAKEALL ipam390 +$ tools/buildman/buildman -k ipam390
-> Now we shall have u-boot.bin
- Create u-boot-uart-ais.bin -$ mono HexAIS_OMAP-L138.exe -entrypoint 0xC1080000 -ini -ipam390-ais-uart.cfg -o ./uboot-uart-ais.bin ./u-boot.bin@0xC1080000; +$ mono HexAIS_OMAP-L138.exe -entrypoint 0xC1080000 -ini ipam390-ais-uart.cfg \ + -o ../current/ipam390/uboot-uart-ais.bin ./u-boot.bin@0xC1080000;
Note: The ipam390-ais-uart.cfg is found in the board directory for the ipam390 board, u-boot:/board/Barix/ipam390/ipam390-ais-uart.cfg diff --git a/doc/README.sha1 b/doc/README.sha1 index f6cca40..f178f37 100644 --- a/doc/README.sha1 +++ b/doc/README.sha1 @@ -51,7 +51,8 @@ c) now calculate the SHA1 sum from the memoryrange and write
Now you have a U-Boot-Image for the pcs440ep board with the correct SHA1 sum.
-If you do a "./MAKEALL pcs440ep" or a "make all" to get the U-Boot image, -the correct SHA1 sum will be automagically included in the U-Boot image. +If you do a "buildman -k pcs440ep" or a "make all" to get the U-Boot image, +which will be found in ../current/ipam390/ - the correct SHA1 sum will be +automagically included in the U-Boot image.
Heiko Schocher, 11 Jul 2007