u-boot.git/include/config_distro_bootcmd.h, branch v2021.04

efi_loader: make the UEFI boot manager configurable

2021-01-20T07:09:34+00:00

Some boards are very tight on the binary size. Booting via UEFI is possible
without using the boot manager.

Provide a configuration option to make the boot manager available.

Signed-off-by: Heinrich Schuchardt

distro_bootcmd: set devtype for dhcp boot

2020-12-15T18:56:50+00:00

Set $devtype for DHCP boot, which can be handy for the boot.scr
for detection of devtype used (for example, when the same boot.scr is
used for both mmc/dhcp boot):

if test ${devtype} = "dhcp"; then
	...
fi

Signed-off-by: Igor Opaniuk 
Reviewed-by: Oleksandr Suvorov

arm: tegra: add options for BOOTENV_EFI_SET_FDTFILE_FALLBACK for tegra186

2020-12-04T20:30:42+00:00

Upstream linux DT naming doesn't align with the U-Boot DT, which may
not always be the case so this allows using BOOTENV_EFI_SET_FDTFILE_FALLBACK
where it might be appropriate for some boards.

Signed-off-by: Peter Robinson 
Signed-off-by: Tom Warren

distro_bootcmd: call EFI bootmgr even without having /EFI/boot

2020-10-06T05:43:56+00:00

Currently, the EFI bootmgr is only called if there is a EFI binary
inside the path for removable media is found, i.e. /EFI/boot/. This
doesn't make sense. It is the duty of the bootmgr to find out the
path and name of the EFI binary to boot. It should be called even
if there is no /EFI/boot directory.

Thus, call the bootmgr before we try to boot the EFI binary inside
the removable media path.

Also remove the ${fdtcontroladdr} parameter because the fallback is
handled in cmd/bootefi.c and that already takes care of correct settings
if the board has ACPI and thus no device tree at all.

Signed-off-by: Michael Walle 
Reviewed-by: Heinrich Schuchardt

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