History log of /openbsd/sys/arch/octeon/stand/rdboot/Makefile (Results 1 – 5 of 5)
Revision Date Author Comments
# 76acbd8d 01-Dec-2019 deraadt <deraadt@openbsd.org>

this hexdump tie-in is incorrect, disable for now


# 3fbdbb31 28-Nov-2019 bluhm <bluhm@openbsd.org>

Implement a hexdump command in the boot loader. This helps to
inspect the memory layout that the firmware has created. It is
especially useful for UEFI debugging.
OK deraadt@ kettenis@


# b5e6f796 04-Aug-2019 visa <visa@openbsd.org>

Revise the way how the octeon bootloader is built. The original
approach was not right, and there is still room for improvement.

OK deraadt@


# 71181cf6 28-Jul-2019 visa <visa@openbsd.org>

Link octeon bootloader to the build.

OK deraadt@


# 3a62b615 17-Jul-2019 visa <visa@openbsd.org>

Add a bootloader for octeon.

The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this d

Add a bootloader for octeon.

The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this device access problem, this new loader has
been built on top of a small kernel. The kernel provides all the
necessary devices drivers, while most of the usual bootloader logic
is in a userspace program in a ramdisk.

The loader program is accompanied by a special device, octboot(4).
The main purpose of this device is to implement a mechanism for
loading and launching kernels. The mechanism has been inspired by Linux'
kexec(2) system call.

The bootloader will be enabled later when it is ready for general use.

Discussed with deraadt@

show more ...