src/sys/boot, branch main

Move sys/boot to stand. Fix all references to new location

2017-11-14T23:02:19+00:00

Sponsored by:	Netflix

Move sys/boot/fdt/dts to sys/dts and adjust scripts.

2017-11-14T21:03:57+00:00

Sponsored by: Netflix

Don't add /boot/dts but /boot/dtb. Stupid think-o. /boot/dtb was

2017-11-13T21:25:57+00:00

what was tested...

Add /boot/dts to the list of default modules. The minimal arm and mips

2017-11-13T21:23:26+00:00

loader.conf for uboot have this in the list, but the default one
didn't. Since there's no harm and it's a failsafe, add it to the list.

Sponsored by: Netflix

Add loader.conf to the list of files that are MD.

2017-11-13T20:39:43+00:00

loader.conf is also different between machines. On arm it's a minimal
one that's not quite compatible with the default one. On arm it's
minimal for speed, which is good, but there's also extra things in it
relative to the default on which break loading FDT which is bad. This
doesn't address that issue, but instead ensures the minimal one for
arm is used.

A similar issue for mips exists, but since we can have a beri variant
of /boot/loader and a uboot variant, I'm leaving that mess alone for
the moment.

Sponsored by: Netflix

Use proper include file. While works, it

2017-11-13T00:30:38+00:00

only works because we have -Isys on the command line. We also have
-Isys/boot/userboot on the command line, so bring it in directly with
. No functional change, but it removes one hard to see
dependency on the boot loader's location in sys/boot.

Sponsored by: Netflix

boot1: also check for NULL device

2017-11-12T17:15:54+00:00

r325681 fixed a NULL pointer dereference on RPi3 caused by a lack of
functionality in uboot's EFI implementation.  That rev checked the boot1
load path for NULL but not the load device.  In practice if the former
works the latter will as well, but improve correctness by checking each
separately.

Submitted by:	Keith White 
Reported by:	jhb
MFC after:	5 days
MFC with:	r325681
Sponsored by:	The FreeBSD Foundation

Make sure the proper loader.rc gets installed.

2017-11-12T17:10:57+00:00

There were two things wrong. First, the wrong path was listed in .PATH
statement. Second, BOOTSRC wasn't yet defined for the .PATH, so it
didn't properly add it. Third, even if these were right, . was in the
path before, so it wouldn't have worked. Replace this with a simple
loop so the proper loader.rc gets selected.

Noticed by: dhw@ (menus stopped working on boot)
Sponsored by: Netflix

Install the 4th files in sys/boot/forth instead of each loader

2017-11-10T23:54:58+00:00

Also, move generation of loader.help into loader.mk. Set HELP_FILES=
to disable this (so we only install one help file, for now). At the
same time remove some duplicate -I lines. Fix several FILES= and
CLEANFILES= into the += form since we're touching both of those in the
.mk files. Make sure we only build one loader.help file per platform
in a unified way (we were building many on some, with the last to
install winning, though often they were the same text).

Also, we're now installing loader.rc and menu.rc everywhere. arm and
mips uboot installed these as menu.rc.sample, but there's no need
since the loader.rc for those platforms doesn't do menu.rc processing
by default. pcibios.4th is now installed everywhere, but will failsafe
on non x86 platforms (it isn't loaded by default anywhere).

These changes are too intertwined to do separately since aspects of
each are required to have a bug-free commit.

Sponsored by: Netflix

Move LOADER_{NO,}_GELI_SUPPORT to MK_LOADER_GELI

2017-11-10T23:54:48+00:00

Transition to WITH/WITHOUT_LOADER_GELI to flag support or not of GELI
in the boot loaders. Add HAVE_GELI so components can flag they need
support (since it's too large to include everywhere). Add temporary
warnings for the old forms to ease transition.

Also, update test script to build without GELI on x86.

Sponsored by: Netflix