d5babd0d | 01-May-2023 |
Warner Losh <imp@FreeBSD.org> |
stand/efi: Simplify code here
We have plenty of stack in the EFI case, so use it instead of the complicated malloc / free dance.
Sponsored by: Netflix Reviewed by: tsoome, kevans Differential Rev
stand/efi: Simplify code here
We have plenty of stack in the EFI case, so use it instead of the complicated malloc / free dance.
Sponsored by: Netflix Reviewed by: tsoome, kevans Differential Revision: https://reviews.freebsd.org/D39415
show more ...
|
43f7eeff | 01-May-2023 |
Warner Losh <imp@FreeBSD.org> |
stand/boot1.efi: Implement bootonce for ZFS
Implement ZFS bootonce protocol. We pass zfs-bootonce=t to the next boot stage as a command line argument. Unlike zfsboot -> loader handoff in the BIOS ca
stand/boot1.efi: Implement bootonce for ZFS
Implement ZFS bootonce protocol. We pass zfs-bootonce=t to the next boot stage as a command line argument. Unlike zfsboot -> loader handoff in the BIOS case, we don't use the OS_BOOTONCE_USED. This would require modifications to loader.efi which would only server to make it more complicated. Instead, use the command line parsing interface for the boot1.efi -> loader.efi to pass in the zfs-bootonce kenv that will be needed by rc.d/zfsbe to activate the BE if boot progresses that far.
Sponsored by: Netflix Reviewed by: tsoome, kevans Differential Revision: https://reviews.freebsd.org/D39412
show more ...
|
88599604 | 11-Feb-2021 |
Mitchell Horne <mhorne@FreeBSD.org> |
loader: always install help files
Address two issues with current help file logic:
The existing condition prevents the common help file from being installed when there are no additional help files
loader: always install help files
Address two issues with current help file logic:
The existing condition prevents the common help file from being installed when there are no additional help files defined. This results in no loader.help on EFI platforms, for example.
Second, due to the fact that we build and install multiple loader types, each successive install will clobber the previous loader.help. The result is that we could lose type-specific commands, or possibly list them in loaders that do not have such commands.
Instead, give each loader type a uniquely named help file. The EFI loader will look for /boot/loader.help.efi, userboot will look for /boot/loader.help.userboot, etc. The interpreter variant has no effect on which help file is loaded.
This leaves the old /boot/loader.help unused.
Some credit for the final approach goes to Mathieu <sigsys@gmail.com> for their version of the fix in https://reviews.freebsd.org/D22951.
PR: 267134 Reported by: Daniel O'Connor <darius@dons.net.au> Reviewed by: imp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D28591
show more ...
|
ad70f2e2 | 11-Jan-2023 |
Warner Losh <imp@FreeBSD.org> |
stand: create common set_currdev
Pull together the nearly identical copies of set_currdev in i386, userboot and efi. Other boot loaders have variances that might be fine to use the common routine, o
stand: create common set_currdev
Pull together the nearly identical copies of set_currdev in i386, userboot and efi. Other boot loaders have variances that might be fine to use the common routine, or not. Since they are harder to test for me, and ofw and uboot do handle these setting differently, leave them be for now.
Sponsored by: Netflix Reviewed by: kevans Differential Revision: https://reviews.freebsd.org/D38005
show more ...
|