[PATCH v2] global: Use proper project name U-Boot (next2)
Michal Simek
michal.simek at amd.com
Fri Sep 15 13:25:27 CEST 2023
On 9/8/23 09:11, Michal Simek wrote:
> Use proper project name in README, rst and comment.
> Done in connection to commit bb922ca3eb4b ("global: Use proper project name
> U-Boot (next)").
>
> Signed-off-by: Michal Simek <michal.simek at amd.com>
> ---
>
> Changes in v2:
> - Revert change in tools/binman/entries.rst reported by Simon
>
> board/cobra5272/README | 18 +++++++++---------
> board/emulation/qemu-ppce500/qemu-ppce500.c | 2 +-
> doc/board/xilinx/zynq.rst | 2 +-
> doc/board/xilinx/zynqmp-r5.rst | 4 ++--
> doc/imx/mkimage/imximage.txt | 2 +-
> doc/usage/environment.rst | 2 +-
> doc/usage/semihosting.rst | 2 +-
> 7 files changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/board/cobra5272/README b/board/cobra5272/README
> index 11abcfacdb6e..0b07148b73a3 100644
> --- a/board/cobra5272/README
> +++ b/board/cobra5272/README
> @@ -1,6 +1,6 @@
> File: README.COBRA5272
> Author: Florian Schlote for Sentec elektronik (linux at sentec-elektronik.de)
> -Contents: This is the README of u-boot (Universal bootloader) for our
> +Contents: This is the README of U-Boot (Universal bootloader) for our
> COBRA5272 board.
> Version: v01.00
> Date: Tue Mar 30 00:28:33 CEST 2004
> @@ -31,7 +31,7 @@ Please refer to u-boot README (general info, u-boot-x-x-x/README),
> to u-boot-x-x-x/board/cobra5272/README and
> to the comments in u-boot-x-x-x/include/configs/cobra5272.h
>
> -Configuring u-boot is done by commenting/uncommenting preprocessor defines.
> +Configuring U-Boot is done by commenting/uncommenting preprocessor defines.
>
> Default configuration is
>
> @@ -48,10 +48,10 @@ Default configuration is
>
>
> #-----------------------------------
> -# u-boot FLASH version & RAM version
> +# U-Boot FLASH version & RAM version
> #-----------------------------------
>
> -The u-boot bootloader for Coldfire processors can be configured
> +The U-Boot bootloader for Coldfire processors can be configured
>
> 1. as a standalone bootloader residing in flash & relocating itself to RAM on
> startup automatically => "FLASH version"
> @@ -60,7 +60,7 @@ The u-boot bootloader for Coldfire processors can be configured
> prestage bootloader ("chainloading") & is running only from the RAM address it
> is linked to => "RAM version"
>
> - This version may be very helpful when installing u-boot for the first time
> + This version may be very helpful when installing U-Boot for the first time
> since it can be used to make available s. th. like a "bootstrap
> mechanism".
>
> @@ -71,7 +71,7 @@ How to build the different images:
> Flash version
> ------------------------------
>
> -Compile u-boot
> +Compile U-Boot
>
> in dir ./u-boot-x-x-x/
>
> @@ -81,14 +81,14 @@ please first check:
>
> CONFIG_MONITOR_IS_IN_RAM has to be not present in the file
>
> - => u-boot as single bootloader starting from flash
> + => U-Boot as single bootloader starting from flash
>
>
> in configs/cobra5272_defconfig CONFIG_TEXT_BASE should be
>
> CONFIG_TEXT_BASE=0xffe00000
>
> - => linking address for u-boot as single bootloader stored in flash
> + => linking address for U-Boot as single bootloader stored in flash
>
> then:
>
> @@ -116,7 +116,7 @@ please modify the settings:
>
> CONFIG_MONITOR_IS_IN_RAM=y
>
> - => u-boot as RAM version, chainloaded by another bootloader or using bdm cable
> + => U-Boot as RAM version, chainloaded by another bootloader or using bdm cable
>
>
> in configs/cobra5272_defconfig CONFIG_TEXT_BASE should be
> diff --git a/board/emulation/qemu-ppce500/qemu-ppce500.c b/board/emulation/qemu-ppce500/qemu-ppce500.c
> index a39bcb4fa0c7..40fd9e5e02b1 100644
> --- a/board/emulation/qemu-ppce500/qemu-ppce500.c
> +++ b/board/emulation/qemu-ppce500/qemu-ppce500.c
> @@ -318,7 +318,7 @@ ulong get_bus_freq(ulong dummy)
> int cpu_numcores(void)
> {
> /*
> - * The QEMU u-boot target only needs to drive the first core,
> + * The QEMU U-Boot target only needs to drive the first core,
> * spinning and device tree nodes get driven by QEMU itself
> */
> return 1;
> diff --git a/doc/board/xilinx/zynq.rst b/doc/board/xilinx/zynq.rst
> index 438912fe42c2..76d67bd62ee9 100644
> --- a/doc/board/xilinx/zynq.rst
> +++ b/doc/board/xilinx/zynq.rst
> @@ -83,7 +83,7 @@ Mainline status
> ---------------
>
> - Added basic board configurations support.
> -- Added zynq u-boot bsp code - arch/arm/mach-zynq
> +- Added zynq U-Boot bsp code - arch/arm/mach-zynq
> - Added zynq boards named - zc70x, zed, microzed, zc770_xm010/xm011/xm012/xm013
> - Added zynq drivers:
>
> diff --git a/doc/board/xilinx/zynqmp-r5.rst b/doc/board/xilinx/zynqmp-r5.rst
> index 2cd368b0308e..266d07d1193f 100644
> --- a/doc/board/xilinx/zynqmp-r5.rst
> +++ b/doc/board/xilinx/zynqmp-r5.rst
> @@ -26,7 +26,7 @@ configure and build armv7 toolchain::
> Notes
> ^^^^^
>
> -Output fragment is u-boot.
> +Output fragment is U-Boot.
>
> Loading
> -------
> @@ -38,7 +38,7 @@ Bootgen
> ^^^^^^^
>
> The first way is to use Xilinx FSBL (First stage
> -bootloader) to load u-boot and start it. The following bif can be used for boot
> +bootloader) to load U-Boot and start it. The following bif can be used for boot
> image generation via Xilinx bootgen utility::
>
>
> diff --git a/doc/imx/mkimage/imximage.txt b/doc/imx/mkimage/imximage.txt
> index f2cf23c5dab8..fa4e486661c2 100644
> --- a/doc/imx/mkimage/imximage.txt
> +++ b/doc/imx/mkimage/imximage.txt
> @@ -213,7 +213,7 @@ Disk identifier: 0xb712a870
> Device Boot Start End Blocks Id System
> /dev/mmcblk0p1 3 16 112455 83 Linux
>
> -I have set 100MB, leaving the first 2 sectors free. I will copy u-boot
> +I have set 100MB, leaving the first 2 sectors free. I will copy U-Boot
> there.
>
> 8. Write the partition table and exit.
> diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
> index c6439dde6689..c57b717caaf3 100644
> --- a/doc/usage/environment.rst
> +++ b/doc/usage/environment.rst
> @@ -216,7 +216,7 @@ fdt_high
> 0xffffffffffffffff (64-bit machines) then
> the fdt will not be copied at all on boot. For this
> to work it must reside in writable memory, have
> - sufficient padding on the end of it for u-boot to
> + sufficient padding on the end of it for U-Boot to
> add the information it needs into it, and the memory
> must be accessible by the kernel. This usage is strongly discouraged
> however as it also stops U-Boot from ensuring the device tree starting
> diff --git a/doc/usage/semihosting.rst b/doc/usage/semihosting.rst
> index 6a280b455e0c..9303a6364d5d 100644
> --- a/doc/usage/semihosting.rst
> +++ b/doc/usage/semihosting.rst
> @@ -23,7 +23,7 @@ eMMC or other NV media are available.
> There are two main ARM virtual Fixed Virtual Platform (FVP) models,
> `Versatile Express (VE) FVP and BASE FVP
> <http://www.arm.com/products/tools/models/fast-models/foundation-model.php>`_.
> -The initial vexpress64 u-boot board created here runs on the VE virtual
> +The initial vexpress64 U-Boot board created here runs on the VE virtual
> platform using the license-free Foundation_v8 simulator. Fortunately,
> the Foundation_v8 simulator also supports the BASE_FVP model which
> companies can purchase licenses for and contain much more functionality.
Applied.
M
More information about the U-Boot
mailing list