u-boot.git/include/config_distro_bootcmd.h, branch v2020.07

NVMe: do PCI enumerate before nvme scan

2019-10-31T11:22:53+00:00

Make sure that the PCI busses are enumerated before trying to
find a NVMe device.

Signed-off-by: Patrick Wildt 
Reviewed-by: Bin Meng

distro_bootcmd: refactor virtio to support PCI block devices

2019-07-24T18:15:38+00:00

Starting libvirt v5.3.0 with QEMU 4.0.0 use of PCI is automatic
and thus storage is connected via PCI, which is not visible to
U-Boot out-of-the-box.

Refactor to do "pci enum" followed by "virtio scan" to see PCI
connected storage, and allow bootloader to load kernel and
initramfs images.

Tested with Fedora/RISCV using releases: libvirt 5.4.0 & 5.5.0,
QEMU 4.0.0 and U-Boot 2019.07 RC4.

Signed-off-by: David Abdurachmanov

config_distro_bootcmd: Init IDE devices

2019-06-21T14:07:11+00:00

IDE devices are no longer automatically probed by u-boot, so it should
be done by the distro boot command before attempting to boot from IDE
(just like scsi and nvme)

Signed-off-by: Joshua Watt

distro: not taint environment variables if possible

2019-02-13T08:40:05+00:00

The aim of this patch is not to have temporary variables used in
distro_bootcmd left as environment variables after run something.
See the discussion[1].
Without this patch, saveenv command also saves those variables, too.
While they are apparently safe, scsi_need_init can be harmful.

Please note that, in most cases, a variable should be converted to
hush's local variable, while "devplist" cannot because it is created
by "part" command as an environment variable.

[1] https://lists.denx.de/pipermail/u-boot/2018-December/350209.html

Signed-off-by: AKASHI Takahiro 
Signed-off-by: Alexander Graf

distro_bootcmd: add NVME support

2019-02-13T08:40:05+00:00

Some boards support NVME drives. We should be able to use them as boot
devices.

NVME access requires running 'nvme scan'.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Simon Glass 
Signed-off-by: Alexander Graf

distro_bootcmd: add VirtIO distro boot command

2018-11-26T05:57:32+00:00

Add a boot command to distro boot to support disks connected over the
VirtIO bus. The boot command uses the shared block environment.

Signed-off-by: Lukas Auer 
Reviewed-by: Bin Meng 
Reviewed-by: Alexander Graf

riscv: rename CPU_RISCV_32/64 to match architecture names ARCH_RV32I/64I

2018-11-26T05:57:29+00:00

RISC-V defines the base integer instruction sets as RV32I and RV64I.
Rename CPU_RISCV_32 and CPU_RISCV_64 to ARCH_RV32I and ARCH_RV64I to
match this convention.

Signed-off-by: Lukas Auer 
Reviewed-by: Bin Meng 
Reviewed-by: Rick Chen

Ability to modify distro boot filename

2018-11-16T21:52:01+00:00

Add in the ability to modify the distro boot filename. Whilst not
immediately useful in normal usage, it allows an alternative
configuration to be provided when other u-boot functionality is used, such
as bootcount limit, to fallback to an alternative boot configuration. In
this case we can follow the same boot path as for normal boot, just
using an alternatively named configuration file.

For example, by providing the following `altbootcmd` when bootcount is in
use:

altbootcmd=setenv boot_extlinx_conf extlinux-rollback.conf; \
	run distro_bootcmd

Signed-off-by: Martyn Welch 
Reviewed-by: Heinrich Schuchardt

efi: sandbox: Add distroboot support

2018-09-23T19:55:30+00:00

With sandbox these values depend on the host system. Let's assume that it
is x86_64 for now.

Signed-off-by: Simon Glass 
Signed-off-by: Alexander Graf

distro: Extend with RISC-V defines

2018-05-29T06:43:12+00:00

While we don't have UEFI naming conventions for RISC-V file paths yet,
we need to search for something. So let's copy the removable file paths
from the RISC-V edk2 port.

Also add the official VCI strings that contain the standardized RISC-V
architecture ID fields.

Signed-off-by: Alexander Graf