Eric Lee / smarc-uboot

Download as
Browse Code ยป

Commit 28fd00b7770b70caa84fac186dcbb09b65eebe5a

Authored by Masahiro Yamada
Committed by Tom Rini
1 parent e619c79ea6
Exists in v2017.01-smarct4x and in 34 other branches 8qm-imx_v2020.04_5.4.70_2.3.0, emb_lf_v2022.04, pitx_8mp_lf_v2020.04, smarc-8m-android-10.0.0_2.6.0, smarc-8m-android-11.0.0_2.0.0, smarc-8mp-android-11.0.0_2.0.0, smarc-imx6_v2018.03_4.14.98_2.0.0_ga, smarc-imx7_v2017.03_4.9.11_1.0.0_ga, smarc-imx7_v2018.03_4.14.98_2.0.0_ga, smarc-imx_v2017.03_4.9.11_1.0.0_ga, smarc-imx_v2017.03_4.9.88_2.0.0_ga, smarc-imx_v2017.03_o8.1.0_1.3.0_8m, smarc-imx_v2018.03_4.14.78_1.0.0_ga, smarc-n7.1.2_2.0.0-ga, smarc-rel_imx_4.1.15_2.0.0_ga, smarc_8m-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8m-imx_v2019.04_4.19.35_1.1.0, smarc_8m_00d0-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2019.04_4.19.35_1.1.0, smarc_8mm-imx_v2020.04_5.4.24_2.1.0, smarc_8mp_lf_v2020.04, smarc_8mq-imx_v2020.04_5.4.24_2.1.0, smarc_8mq_lf_v2020.04, ti-u-boot-2015.07, v2015.07-smarct33, v2015.07-smarct33-emmc, v2015.07-smarct4x, v2016.05-dlt, v2016.05-smarct3x, v2016.05-smarct3x-emmc, v2016.05-smarct4x, v2017.01-smarct3x, v2017.01-smarct3x-emmc

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>

Showing 1 changed file with 6 additions and 6 deletions Side-by-side Diff

... ... @@ -28,7 +28,7 @@
28 28  
29 29 This model assumes that boards will load boot configuration files from a
30 30 regular storage mechanism (eMMC, SD card, USB Disk, SATA disk, etc.) with
31   -a standard partitioning scheme (MBR, GPT). Boards that cannnot support this
  31 +a standard partitioning scheme (MBR, GPT). Boards that cannot support this
32 32 storage model are outside the scope of this document, and may still need
33 33 board-specific installer/boot-configuration support in a distro.
34 34  
... ... @@ -37,9 +37,9 @@
37 37 flash before running the distro installer. Even on boards that do not conform
38 38 to this aspect of the model, the extent of the board-specific support in the
39 39 distro installer logic would be to install a board-specific U-Boot package to
40   -the boot partition partition during installation. This distro-supplied U-Boot
41   -can still implement the same features as on any other board, and hence the
42   -distro's boot configuration file generation logic can still be board-agnostic.
  40 +the boot partition during installation. This distro-supplied U-Boot can still
  41 +implement the same features as on any other board, and hence the distro's boot
  42 +configuration file generation logic can still be board-agnostic.
43 43  
44 44 Locating Bootable Disks
45 45 -----------------------
... ... @@ -61,7 +61,7 @@
61 61 conceptually identical to creating a grub2 configuration file on a desktop
62 62 PC.
63 63  
64   -Note that in the absense of any partition that is explicitly marked bootable,
  64 +Note that in the absence of any partition that is explicitly marked bootable,
65 65 U-Boot falls back to searching the first valid partition of a disk for boot
66 66 configuration files. Other bootloaders are recommended to do the same, since
67 67 I believe that partition table bootable flags aren't so commonly used outside
... ... @@ -238,7 +238,7 @@
238 238 The kernel should be located within the first 128M of RAM in order for the
239 239 kernel CONFIG_AUTO_ZRELADDR option to work, which is likely enabled on any
240 240 distro kernel. Since the kernel will decompress itself to 0x8000 after the
241   - start of RAM, kernel_addr_rshould not overlap that area, or the kernel will
  241 + start of RAM, kernel_addr_r should not overlap that area, or the kernel will
242 242 have to copy itself somewhere else first before decompression.
243 243  
244 244 A size of 16MB for the kernel is likely adequate.