When loading a device tree using the "mach dtb" command, give firmware
a chance to make modifications (such as applying memory reservations)
by using the EFI devicetree fixup protocol.

ok jca@

Invalidating the D-cache after disabling it turned out to be a bad idea
and broke Allwinner SoCs with Cortex-A7 cores. So skip that and also
invalidate the I-cache before disabling it. This seems t

Invalidating the D-cache after disabling it turned out to be a bad idea
and broke Allwinner SoCs with Cortex-A7 cores. So skip that and also
invalidate the I-cache before disabling it. This seems to work better
on a wide range of boards.

ok deraadt@, jmatthew@

show more ...

Flush the D-cache before we disable the cache. This makes more sense and
fixes booting on my A10S-OLinuXino-MICRO board. Since the cache is still
enabled, the CPU might bring back some of the cache

Flush the D-cache before we disable the cache. This makes more sense and
fixes booting on my A10S-OLinuXino-MICRO board. Since the cache is still
enabled, the CPU might bring back some of the cache lines we just flushed.
So invalidate the cache after disabling.

ok deraadt@

show more ...

Bring over various changes from the arm64 version of this code.

ok patrick@

Add openbsd,dma-constraint property to /chosen node on armv7

On the Zynq-7000, the DMA constraint has to be adjusted because many
bus masters are unable to access the lowest part of RAM.

OK patrick

Add openbsd,dma-constraint property to /chosen node on armv7

On the Zynq-7000, the DMA constraint has to be adjusted because many
bus masters are unable to access the lowest part of RAM.

OK patrick@ kettenis@

show more ...

Oops. Forgot to commit the version bump.

Make sure that switching the console from serial to framebuffer works
for framebuffer nodes under / and /chosen.

Same change made to arm64 last month.

Use daddr_t and not daddr32_t in boot media.

At a minimum, amd64/i386 should now boot from 4TB GPT formatted disks.

More daddr32_t terminations with extreme prejudice to follow.

Tested by various,

Use daddr_t and not daddr32_t in boot media.

At a minimum, amd64/i386 should now boot from 4TB GPT formatted disks.

More daddr32_t terminations with extreme prejudice to follow.

Tested by various, in snaps for a few days.

ok deraadt@

show more ...

increment version numbers, due to recent RB_GOODSEED and fchmod +T changes

Our check to see if the EFI services support Mtftp() doesn't work
on U-Boot anymore, since we checked if the method is provided, but
now U-Boot provides a simple stub that only returns EFI_UNSUPPORTE

Our check to see if the EFI services support Mtftp() doesn't work
on U-Boot anymore, since we checked if the method is provided, but
now U-Boot provides a simple stub that only returns EFI_UNSUPPORTED.
A proper UEFI would throw EFI_INVALID_PARAMETER if we pass NULL
as first parameter, but U-Boot doesn't. This way we can see if
the method is actually provided and not just a stub.

ok kettenis@

show more ...

Remove board ID support. 6.7 shipped with a kernel that doesn't need
it anymore.

jsg@

Port "mach dtb" code from arm64.

ok patrick@

Make efi_device_path_depth() return the full device path depth if we don't
find a media device path node. Fixes booting OpenBSD on some older U-Boot
versions that are in wide circulation such as 201

Make efi_device_path_depth() return the full device path depth if we don't
find a media device path node. Fixes booting OpenBSD on some older U-Boot
versions that are in wide circulation such as 2017.09 and 2017.11.

ok patrick@

show more ...

Allow armv7 efiboot(8) to read from an ffs2 filesystem. ok kettenis@

Add the capability to boot from another block device than the one that
efiboot was loaded from. Code taken from arm64 with softraid support
dropped for now.

ok jsg@

Use arc4 to bit-spread the 512-byte random buffer over the .openbsd.randomdata
section, which has grown a fair bit with the introduction of retguard.
Mortimer discovered the repeated 512-byte sequenc

Use arc4 to bit-spread the 512-byte random buffer over the .openbsd.randomdata
section, which has grown a fair bit with the introduction of retguard.
Mortimer discovered the repeated 512-byte sequence as retguard keys, and
this resolves the issue. (Chacha does not fit on the media, so 1.5K early
drop RC4 is hopefully sufficient in our KARL link universe)
Version crank the bootblocks. sysupgrade -s will install new bootblocks.
ok djm mortimer

show more ...

Make it possible to switch to framebuffer "glass" console in case it
isn't the default already. Same change as we made on arm64 two months ago.

ok patrick@

Allow PXE booting using u-boot by relaxing our requirements
of the EFI PXE protocol. This also brings us in line with
the GRUB2 implementation.

Tested by naddy@ to behave the same
Tested by sven fa

Allow PXE booting using u-boot by relaxing our requirements
of the EFI PXE protocol. This also brings us in line with
the GRUB2 implementation.

Tested by naddy@ to behave the same
Tested by sven falempin on his Pine64

show more ...

crank version, following fchmod change

In the bootblocks, after discovering and opening /bsd.upgrade, fchmod -x
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script

In the bootblocks, after discovering and opening /bsd.upgrade, fchmod -x
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade.
Now various forms of upgrade failure will reboot into /bsd, which is probably
more recoverable. Performing fchmod -x depends on (1) use of MI boot.c
(not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality
in the IO layer. Most architectures have this support now.

Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will
remain in the tree while refinements happen for some of the laggard
architectures.

based upon a discussion florian
tested in snapshots for more than a week without any complaints

show more ...

Disable caches and MMU before jumping to the kernel entry point. Needed
because UEFI on 32-bit ARM is supposed to leave them enabled and U-boot
was changed (starting with release 2019.04) to follow

Disable caches and MMU before jumping to the kernel entry point. Needed
because UEFI on 32-bit ARM is supposed to leave them enabled and U-boot
was changed (starting with release 2019.04) to follow the spec here. However
the OpenBSD/armv7 kernel expects to be booted with caches and MMU turned off.

Note that there are still issues on boards that enable the non-architected
L2 cache. UEFI demands that such caches are not turned on, but U-Boot
does turn them on and this makes our kernel fail to boot.

With help from jsg@

ok jsg@

show more ...

crank versions

crank version; looks good deraadt

Port arm64's network boot efforts to armv7 as well now that there is
support for using U-Boot's network layer. Since arm64 and armv7's
efiboot(8) have the same heritance the diffs from arm64 simply

Port arm64's network boot efforts to armv7 as well now that there is
support for using U-Boot's network layer. Since arm64 and armv7's
efiboot(8) have the same heritance the diffs from arm64 simply applied
to armv7.

show more ...

If you use sys/param.h, you don't need sys/types.h