The clock on RISC-V is architectural, so we really don't need the
authorkettenis <kettenis@openbsd.org>
Tue, 4 May 2021 16:38:06 +0000 (16:38 +0000)
committerkettenis <kettenis@openbsd.org>
Tue, 4 May 2021 16:38:06 +0000 (16:38 +0000)
commit420b129f941aa8cb4634bcb1a5b42b47767b6e06
tree8f2a0cc0444775b1dfdf7db27be1f765a82fbb8c
parent2795574053f7addabf6fb8e3ed5d47c8a33b3c7a
The clock on RISC-V is architectural, so we really don't need the
whole abstraction layer to support multiple timers.  And we don't
really need a separate driver.  Replace timer(4) with code based on
the powerpc64 implementation of the randomized statclock code.

Fixes hangs seen on real hardware.

ok jsg@, drahn@
sys/arch/riscv64/conf/GENERIC
sys/arch/riscv64/conf/RAMDISK
sys/arch/riscv64/conf/files.riscv64
sys/arch/riscv64/dev/mainbus.c
sys/arch/riscv64/dev/timer.c [deleted file]
sys/arch/riscv64/dev/timer.h [deleted file]
sys/arch/riscv64/include/cpu.h
sys/arch/riscv64/riscv64/clock.c [new file with mode: 0644]
sys/arch/riscv64/riscv64/cpu.c
sys/arch/riscv64/riscv64/intr.c
sys/arch/riscv64/riscv64/machdep.c