On Mon, Mar 19, 2018 at 11:51 AM, Andriy Gapon <a...@freebsd.org> wrote:
> On 19/03/2018 18:20, John Baldwin wrote: > > On Monday, March 19, 2018 03:27:53 PM Kyle Evans wrote: > >> Author: kevans > >> Date: Mon Mar 19 15:27:53 2018 > >> New Revision: 331209 > >> URL: https://svnweb.freebsd.org/changeset/base/331209 > >> > >> Log: > >> Add note to UPDATING about UEFI changes requiring loader(8) update > >> > >> These problems have only been observed with boards using U-Boot (e.g. > ARM) > >> where virtual addresses are already set in the memory map by the > firmware > >> and the firmware is expecting a call to SetVirtualAddressMap to be > made. > >> I refrain from mentioning this in the note because this could also be > the > >> case on some not-yet-tested firmware on amd64 and it's not a bad > >> recommendation for the general case. > > > > How does this fit with the recommended installation steps of doing > > 'make installkernel' and rebooting before doing a 'make installworld'? > > Installation of /boot/loader along with likes of cat and cut has always > puzzled > me very much. > Historical reason. We've always installed /boot/loader with installworld. We also install the other boot loaders, but don't deploy them (so there's a new /boot/boot, but it isn't installed into /). To get around this issue, though, is trivial: make installkenrel cd stand make install reboot make installworld in this weird case. Warner _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
