diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2015-07-07 18:47:17 +0900 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2015-07-08 18:26:41 -0400 |
| commit | 28fd00b7770b70caa84fac186dcbb09b65eebe5a (patch) | |
| tree | 1b2725c72d8dea1f3d47a6fba649b27d0b9538f8 /doc | |
| parent | e619c79ea60f9d16c62aca05cb513e2f244d0dc5 (diff) | |
| download | u-boot-28fd00b7770b70caa84fac186dcbb09b65eebe5a.tar.gz u-boot-28fd00b7770b70caa84fac186dcbb09b65eebe5a.tar.bz2 u-boot-28fd00b7770b70caa84fac186dcbb09b65eebe5a.zip | |
README.distro: fix typos
The word "partition" is doubled. Keep decent forms for the
following lines.
Also, fix some other typos while we are here.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.distro | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/README.distro b/doc/README.distro index 0308a4c73a..9e4722a86e 100644 --- a/doc/README.distro +++ b/doc/README.distro @@ -28,7 +28,7 @@ decoupling distro install/boot logic from any knowledge of the bootloader. This model assumes that boards will load boot configuration files from a regular storage mechanism (eMMC, SD card, USB Disk, SATA disk, etc.) with -a standard partitioning scheme (MBR, GPT). Boards that cannnot support this +a standard partitioning scheme (MBR, GPT). Boards that cannot support this storage model are outside the scope of this document, and may still need board-specific installer/boot-configuration support in a distro. @@ -37,9 +37,9 @@ that contains U-Boot, and that the user has somehow installed U-Boot to this flash before running the distro installer. Even on boards that do not conform to this aspect of the model, the extent of the board-specific support in the distro installer logic would be to install a board-specific U-Boot package to -the boot partition partition during installation. This distro-supplied U-Boot -can still implement the same features as on any other board, and hence the -distro's boot configuration file generation logic can still be board-agnostic. +the boot partition during installation. This distro-supplied U-Boot can still +implement the same features as on any other board, and hence the distro's boot +configuration file generation logic can still be board-agnostic. Locating Bootable Disks ----------------------- @@ -61,7 +61,7 @@ any other bootloader) will find those boot files and execute them. This is conceptually identical to creating a grub2 configuration file on a desktop PC. -Note that in the absense of any partition that is explicitly marked bootable, +Note that in the absence of any partition that is explicitly marked bootable, U-Boot falls back to searching the first valid partition of a disk for boot configuration files. Other bootloaders are recommended to do the same, since I believe that partition table bootable flags aren't so commonly used outside @@ -238,7 +238,7 @@ kernel_addr_r: The kernel should be located within the first 128M of RAM in order for the kernel CONFIG_AUTO_ZRELADDR option to work, which is likely enabled on any distro kernel. Since the kernel will decompress itself to 0x8000 after the - start of RAM, kernel_addr_rshould not overlap that area, or the kernel will + start of RAM, kernel_addr_r should not overlap that area, or the kernel will have to copy itself somewhere else first before decompression. A size of 16MB for the kernel is likely adequate. |