doc: fix references to distro documentation

Commit 37c5195dfc ("doc: Move distro boot doc to rST") renamed
doc/README.distro to doc/develop/distro.rst.

Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Reviewed-by: Soeren Moch <smoch@web.de>
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
This commit is contained in:
Dario Binacchi 2023-01-09 12:52:40 +01:00 committed by Heinrich Schuchardt
parent b1315ad333
commit 5ef229a007
5 changed files with 6 additions and 5 deletions

View file

@ -177,7 +177,7 @@ To restore GUID partition table one needs to:
"name=u-boot,size=60MiB;name=boot,size=60Mib,bootable;name=rootfs,size=0" "name=u-boot,size=60MiB;name=boot,size=60Mib,bootable;name=rootfs,size=0"
It can be used to locate bootable disks with command It can be used to locate bootable disks with command
"part list <interface> <dev> -bootable <varname>", "part list <interface> <dev> -bootable <varname>",
please check out doc/README.distro for use. please check out doc/develop/distro.rst for use.
2. Define 'CONFIG_EFI_PARTITION' and 'CONFIG_CMD_GPT' 2. Define 'CONFIG_EFI_PARTITION' and 'CONFIG_CMD_GPT'

View file

@ -336,7 +336,7 @@ Deployment for Distro Boot
-------------------------- --------------------------
UniPhier SoC family boot the kernel in a generic manner as described in UniPhier SoC family boot the kernel in a generic manner as described in
doc/README.distro . doc/develop/distro.rst.
To boot the kernel, you need to deploy necesssary components to a file To boot the kernel, you need to deploy necesssary components to a file
system on one of your block devices (eMMC, NAND, USB drive, etc.). system on one of your block devices (eMMC, NAND, USB drive, etc.).

View file

@ -57,7 +57,8 @@ to instantiate. Note, the maximum supported CPU number in QEMU is 255.
U-Boot uses 'distro_bootcmd' by default when booting on x86 QEMU. This tries to U-Boot uses 'distro_bootcmd' by default when booting on x86 QEMU. This tries to
load a boot script, kernel, and ramdisk from several different interfaces. For load a boot script, kernel, and ramdisk from several different interfaces. For
the default boot order, see 'qemu-x86.h'. For more information, see the default boot order, see 'qemu-x86.h'. For more information, see
'README.distro'. Most Linux distros can be booted by writing a uboot script. 'doc/develop/distro.rst'. Most Linux distros can be booted by writing a uboot
script.
For example, Debian (stretch) can be booted by creating a script file named For example, Debian (stretch) can be booted by creating a script file named
'boot.txt' with the contents:: 'boot.txt' with the contents::

View file

@ -478,7 +478,7 @@ or:
+-------+--------+---------+------------------------+------------------------+ +-------+--------+---------+------------------------+------------------------+
And the 4th partition (Rootfs) is marked bootable with a file extlinux.conf And the 4th partition (Rootfs) is marked bootable with a file extlinux.conf
following the Generic Distribution feature (doc/README.distro for use). following the Generic Distribution feature (doc/develop/distro.rst for use).
The size of fip or ssbl partition must be enough for the associated binary file, The size of fip or ssbl partition must be enough for the associated binary file,
4MB and 2MB are default values. 4MB and 2MB are default values.

View file

@ -181,7 +181,7 @@ If that fails it will then try to boot from several interfaces using
'distro_bootcmd': It will first try to boot from the microSD slot, then the 'distro_bootcmd': It will first try to boot from the microSD slot, then the
SD slot, then the internal eMMC, then the SATA interface and finally the USB SD slot, then the internal eMMC, then the SATA interface and finally the USB
interface. For more information on how to configure your distribution to boot, interface. For more information on how to configure your distribution to boot,
see 'README.distro'. see 'doc/develop/distro.rst'.
Links: Links:
------ ------