On Tue, Jun 01, 2021 at 01:43:32AM +0200, Leon Fischer wrote: > The mkuboot(8) man page was not updated after this commit: > > RCS file: /cvs/src/usr.sbin/mkuboot/mkuboot.c,v > ---------------------------- > revision 1.7 > date: 2016/12/20 11:27:11; author: jsg; state: Exp; lines: +3 -1; > commitid: fELL92HBrGHkYVvc; > Add the u-boot arm64 architecture number and map it to "aarch64" to > match OpenBSD/arm64 MACHINE_ARCH. > > ok patrick@ > ---------------------------- > > Here's a patch to add it to the supported architectures list.
thanks, committed > > This man page is still missing a few things: what is "infile", what do > the types mean, an example for installing the image, etc. Before there were armv7/arm64 efi bootloaders kernels used to require having a U-Boot header and had to reside on a fat/ext filesystem. With boot scripts created by something like 'mkuboot -t script -a arm -o linux boot.cmd boot.scr' with boot.scr also placed on the fat/ext filesystem. boot.cmd being a text file with U-Boot commands. Now U-Boot supports uefi and generic distro boot there isn't a need to use mkuboot for the most part. > > Index: mkuboot.8 > =================================================================== > RCS file: /cvs/src/usr.sbin/mkuboot/mkuboot.8,v > retrieving revision 1.1 > diff -u -p -r1.1 mkuboot.8 > --- mkuboot.8 30 May 2013 19:17:15 -0000 1.1 > +++ mkuboot.8 31 May 2021 23:30:54 -0000 > @@ -65,6 +65,7 @@ The following arguments are valid as the > .Ar arch > parameter: > .Bd -unfilled -offset indent -compact > +aarch64 > alpha > amd64 > arm > >
