remove unused armv7 max_processes global
ok miod@

Reorganize the EFI code a bit. Move the efi.h header from dev/acpi to
dev/efi and rename the arm64 efi.c to efi_machdep.c, preparing the way
for MI EFI code and an amd64 implementation of EFI runtim

Reorganize the EFI code a bit. Move the efi.h header from dev/acpi to
dev/efi and rename the arm64 efi.c to efi_machdep.c, preparing the way
for MI EFI code and an amd64 implementation of EFI runtime support.

ok deraadt@, mlarkin@

show more ...

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 ...

remove uneeded includes in md armv7 files

based on include-what-you-use suggestions

spelling

introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.

rnd.c uses nanotime to get access to some bits that change quickly
between events that it can mix into the entropy pool. it do

introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.

rnd.c uses nanotime to get access to some bits that change quickly
between events that it can mix into the entropy pool. it doesn't
use nanotime to get a monotonically increasing set or ordered and
accurate timestamps, it just wants something with bits that change.

there's been discussions for years about letting rnd use a clock
that's super fast to read, but not necessarily accurate, but it
wasn't until recently that i figured out it wasn't interested in
time at all, so things like keeping a fast clock coherent between
cpu cores or correct according to ntp is unecessary. this means we
can just let rnd read the cycle counters on cpus and things will
be fine. cpus with cycle counters that vary in their speed and
arent kept consistent between cores may even be desirable in this
context.

so this is the first step in converting rnd.c to reading cycle
counter. it copies the nanotime backend to each arch, and they can
replace it with something MD as a second step later on.

djm@ suggested rnd_messybytes, but we landed on cpu_rnd_messybits.
thanks to visa for his eyes.
ok deraadt@ visa@
deraadt@ says he will help handle any MD fallout that occurs.

show more ...

Look at the openbsd,boothowto property and bring the bootarg parsing
code in line with arm64.

ok deraadt@

Kill board_id variable; its last consumer is gone now.

ok jsg@

Whitespace removal

Pointed out by Jerome Pinot

fast track ddb> reboot command to skip anything which might panic again.
ok deraadt

Use EFI memory map to determine what memory regions are availble just like
we already do on arm64. Prevents using the framebuffer on the cubox-i as
regular memory for example.

Make it possible to build a MULTIPROCESSOR kernel on armv7. While this
doesn't actually spin up any secondary CPUs, it does run. Mostly a cleanup
of <machine/cpu.h> along the lines of what I did ea

Make it possible to build a MULTIPROCESSOR kernel on armv7. While this
doesn't actually spin up any secondary CPUs, it does run. Mostly a cleanup
of <machine/cpu.h> along the lines of what I did earlier on arm64. Makes
armv7 use the MI mplock implementation and implements copyin32.

ok patrick@

show more ...

Remove comcnspeed and comcnmode. They serve no purpose anymore. Configuring
the serial port speed can be done through the device tree and these days
everybody uses 8N1 for the mode.

ok patrick@, v

Remove comcnspeed and comcnmode. They serve no purpose anymore. Configuring
the serial port speed can be done through the device tree and these days
everybody uses 8N1 for the mode.

ok patrick@, visa@, jsg@

show more ...

Remove a4x bus space hack.

ok patrick@

Use speed from device tree for serial console on armv7 too.

ok visa@, patrick@

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 ...

Rework and cleanup the linker script for armv7. The main feature is
that it gives us a read-only data section. In addition the linker
script is now easily diffable to arm64 and we also stop mapping

Rework and cleanup the linker script for armv7. The main feature is
that it gives us a read-only data section. In addition the linker
script is now easily diffable to arm64 and we also stop mapping some
unnecessary space before the kernel.

Prompted by deraadt@
ok kettenis@

show more ...

Zap silly diagnostic reboot message.

ok bmercer@, deraadt@

Rename Debugger() into db_enter().

Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.

ok deraadt@, kettenis@, visa@

Mainline u-boot on the ClearFog seems to insert an empty memory region
into the /memory node which we happily physload into UVM. This leads
to a quickly panic(9)ing system when there is actual physi

Mainline u-boot on the ClearFog seems to insert an empty memory region
into the /memory node which we happily physload into UVM. This leads
to a quickly panic(9)ing system when there is actual physical memory
starting at zero due to how the physeg array is sorted when using the
binary search strategy. To fix this, do not physload an empty memory
region.

ok jsg@ kettenis@

show more ...

Lookup the /memory node again after we reinit the FDT. This makes adding
additional memory segments provided by the device tree actually work.

ok jsg@

Remove now unused disable_l2_if_needed interface.
ok kettenis@ patrick@

Add a power down function pointer so power down can work without the
platform abstraction.

ok tom@ kettenis@

Simplify handling of cold reboot on armv7 to match other platforms

Suggested by and ok both patrick@ and kettenis@

Some device trees use 64-bit intermediate virtual addresses. This
means that even though the hardware in the end never leaves the 32-bit
address space, some addresses used solely in the device tree

Some device trees use 64-bit intermediate virtual addresses. This
means that even though the hardware in the end never leaves the 32-bit
address space, some addresses used solely in the device tree can be
bigger than 32-bit. As bus_space_map(9) takes addresses of size
bus_addr_t, which is 32-bit on ARMv7, we cannot pass those virtual
addresses to the parent bus, even though it will be mapped back into a
32-bit address in the end. To work around this, make bus_space_map(9)
take a 64-bit address. Since this is implemented as a macro and
function pointer we can safely do that without harming any other
architecture.

ok kettenis@ deraadt@

show more ...