stsp [Wed, 30 Jun 2021 09:46:46 +0000 (09:46 +0000)]
Make Tx-done interrupt processing in iwx(4) more similar to iwlwifi.
When iwx(4) takes a frame off the queue we used the ring index reported
by firmware to figure out which frame can be taken off the ring.
This logic was inherited from iwn(4).
We have sometimes seen an index get skipped and had a workaround in place
where we took all pending frames up to this index off the ring.
Apart from the ring index the firmware reports another value which is its
starting sequence number (SSN). An SSN is usually associated with a Tx
aggregation queue that uses block ack. On non-aggregation queues the SSN
matches the ring index most of the time and hence seems redundant at first
sight. But the values are not always the same.
We now always use the SSN as the upper bound which matches the Linux driver.
This seems to fix fatal firmware errors during Tx commands seen by jcs@
which suggests that we were sometimes taking frames off the ring too early.
stsp [Wed, 30 Jun 2021 09:45:47 +0000 (09:45 +0000)]
Fix Tx queue flushing in iwm(4).
iwm(4) was still using an outdated version of the TX_FLUSH command.
Current firmware expects a different version which has the same size but
different semantics. The iwx(4) driver is already using the new version.
Also do not log errors if flushing Tx queues fails. This can happen if
the AP disappeared. Just cope by resetting the device and clearing rings.
Should fix "flushing Tx queues failed" and related firmware errors.
stsp [Wed, 30 Jun 2021 09:44:56 +0000 (09:44 +0000)]
Align HT protection flags we send to iwm(4) firmware with flags used by
Linux iwlwifi.
Setting the FAT protection flag while we're using 20 MHz channels doesn't
really make a lot of sense to me but apparently firmware expects it to be
set regardless. Linux does not use the SELF_CTS_EN flag so it might be better
to avoid using SELF_CTS_EN.
According to zxystd from OpenIntelWireless, the same change fixed fatal
firmware errors seen during HT protection updates for them:
https://github.com/OpenIntelWireless/itlwm/commit/
032a14185a434b7181c0e78a953dc2e1c21a0853
test and ok gnezdo@
stsp [Wed, 30 Jun 2021 09:43:59 +0000 (09:43 +0000)]
Make the iwm(4) mac context task send its command only if we are still in
RUN state when the task gets to run. Fixes fatal firmware errors where
mac context updates were erroneously sent in states other than RUN state.
Additionally, avoid scheduling a mac context task if a pending newstate
task is going to move us out of RUN state anyway.
Issue debugged by zxystd in OpenIntelWireless itlwm; patch by me.
stsp [Wed, 30 Jun 2021 09:42:22 +0000 (09:42 +0000)]
Make Tx-done interrupt processing in iwm(4) more similar to iwlwifi.
When iwm(4) takes a frame off a non-aggregation queue we used the ring index
reported by firmware to figure out which frame can be taken off the ring.
This logic was inherited from iwn(4).
We have sometimes seen an index get skipped and had a workaround in place
where we took all pending frames up to this index off the ring.
Apart from the ring index the firmware reports another value which is its
starting sequence number (SSN). An SSN is usually associated with a Tx
aggregation queue that uses block ack. On non-aggregation queues the SSN
matches the ring index most of the time and hence seems redundant at first
sight. But the values are not always the same.
We now always use the SSN as the upper bound which matches the Linux driver.
This seems to fix fatal firmware errors during Tx commands seen by jcs@
which suggests that we were sometimes taking frames off the ring too early.
The ring index is still used to feed information about a frame to the Tx
rate control algorithm but no longer determines when frames are taken off
the ring.
test and ok jcs@
jsg [Wed, 30 Jun 2021 07:39:05 +0000 (07:39 +0000)]
add missing call to sbi_remote_fence_i()
ok kettenis@
jsg [Wed, 30 Jun 2021 01:08:10 +0000 (01:08 +0000)]
MULTIPTOCESSOR -> MULTIPROCESSOR
ok deraadt@
deraadt [Tue, 29 Jun 2021 22:41:12 +0000 (22:41 +0000)]
sync
deraadt [Tue, 29 Jun 2021 22:03:50 +0000 (22:03 +0000)]
include bsd.mp (but don't change isntall.md to choose it yet)
deraadt [Tue, 29 Jun 2021 22:03:30 +0000 (22:03 +0000)]
build bsd.mp
kettenis [Tue, 29 Jun 2021 21:31:49 +0000 (21:31 +0000)]
Didn't intend to commit the CPU_IS_RUNNING() changes just yet, so revert
those bits.
kettenis [Tue, 29 Jun 2021 21:27:52 +0000 (21:27 +0000)]
SMP support. Mostly works, but occasionally craps out during boot.
ok drahn@
kettenis [Tue, 29 Jun 2021 19:58:21 +0000 (19:58 +0000)]
whitespace
deraadt [Tue, 29 Jun 2021 19:57:23 +0000 (19:57 +0000)]
sync
jsing [Tue, 29 Jun 2021 19:56:11 +0000 (19:56 +0000)]
Pull sigalg selection up into ssl3_send_client_verify().
This means that we do sigalg selection for all cases, including those
where are are not sending sigalgs. This is needed in order to track our
signature type in legacy cases.
ok tb@
jsing [Tue, 29 Jun 2021 19:43:15 +0000 (19:43 +0000)]
Track sigalg used by ourselves and our peer in the legacy stack.
This is needed for upcoming API additions.
jsing [Tue, 29 Jun 2021 19:36:14 +0000 (19:36 +0000)]
Pull up and dedup the TLS version check in ssl_sigalg_pkey_ok().
Suggested by tb@
jsing [Tue, 29 Jun 2021 19:33:46 +0000 (19:33 +0000)]
Simplify RSA PSS key size comment.
Wording provided by tb@
jsing [Tue, 29 Jun 2021 19:31:16 +0000 (19:31 +0000)]
Use appropriate TLS version when building client sigalg extensions.
Only use the minimum TLS version to when building a signature algorithms
extension for a ClientHello - in all other cases we should be using the
negotiated TLS version.
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 19:29:16 +0000 (19:29 +0000)]
Change ssl_sigalg_from_value() to take SSL * instead of a TLS version.
This simplifies callers, as only the negotiated TLS version needs to be
used here.
Requested by tb@
jsing [Tue, 29 Jun 2021 19:25:59 +0000 (19:25 +0000)]
Make various sigalg functions static now that they're only used internally.
jsing [Tue, 29 Jun 2021 19:24:07 +0000 (19:24 +0000)]
Convert legacy stack server to ssl_sigalg_for_peer().
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 19:23:36 +0000 (19:23 +0000)]
Convert legacy stack client to ssl_sigalg_for_peer().
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 19:20:39 +0000 (19:20 +0000)]
Provide a ssl_sigalg_for_peer() function and use in the TLSv1.3 code.
Provide an ssl_sigalg_for_peer() function that knows how to figure out
which signature algorithm should be used for a peer provided signature,
performing appropriate validation to ensure that the peer provided value
is suitable for the protocol version and key in use.
In the TLSv1.3 code, this replaces the need for separate calls to lookup
the sigalg from the peer provided value, then perform validation.
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 19:10:08 +0000 (19:10 +0000)]
Move the RSA-PSS check for TLSv1.3 to ssl_sigalg_pkey_ok().
Also, rather than passing in a check_curve flag, pass in the SSL * and
handle version checks internally to ssl_sigalg_pkey_ok(), simplifying
the callers.
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 18:59:25 +0000 (18:59 +0000)]
Factor out handling of legacy default signature algorithms.
In the case of TLSv1.0 and TLSv1.1 there is no signature algorithms
extension and default signature algorithms are used - similar applies to
TLSv1.2 when the signature algorithms extension has been omitted.
ok inoguchi@ tb@
jsing [Tue, 29 Jun 2021 18:55:47 +0000 (18:55 +0000)]
Mop up now unused variables.
jsing [Tue, 29 Jun 2021 18:47:15 +0000 (18:47 +0000)]
Require a ServerHello following a HelloRetryRequest to use the same cipher.
RFC 8446 section 4.1.4 requires that the client ensure the cipher suite
in the TLSv1.3 HelloRetryRequest and subsequent ServerHello is the same.
Reported via GitHub issue #675.
ok inoguchi@ tb@
deraadt [Tue, 29 Jun 2021 18:45:41 +0000 (18:45 +0000)]
delete pre-EFI boot kernel location scripting
ok drahn
jsing [Tue, 29 Jun 2021 18:43:49 +0000 (18:43 +0000)]
Reject zero-length non-application data fragments in the legacy stack.
Per RFC 5246 section 6.2.1, zero-length fragments are only permitted for
application data - reject all others.
Reported via GitHub issue #675.
ok inoguchi@ tb@
matthieu [Tue, 29 Jun 2021 17:49:49 +0000 (17:49 +0000)]
sync maxusers with other 64bits architectures. ok kettenis@, deraadt@.
deraadt [Tue, 29 Jun 2021 17:43:57 +0000 (17:43 +0000)]
Flip the -r RRDP switch, which went through community testing for half a year.
Default is now to attempt RRDP first, then try RSYNC.
If problems show up, return to rsync-only behaviour with -R, and file a report.
ok claudio
schwarze [Tue, 29 Jun 2021 16:34:52 +0000 (16:34 +0000)]
more precision because the argument is signed,
and even char is signed on some platforms;
OK millert@ jmc@
claudio [Tue, 29 Jun 2021 16:15:37 +0000 (16:15 +0000)]
remove unused prototype
OK deraadt@
tobhe [Tue, 29 Jun 2021 15:39:20 +0000 (15:39 +0000)]
Send AUTHENTICATION_FAILED in case of unexpected auth method or auth
data not being accessible.
From Claudia Priesterjahn @ achelos
ok patrick@
schwarze [Tue, 29 Jun 2021 14:47:33 +0000 (14:47 +0000)]
function args must not use .Ar and EDOM and ERANGE require .Er;
mostly mechanical diff similar to what Emil Engler just sent for sqrt(3)
schwarze [Tue, 29 Jun 2021 14:46:44 +0000 (14:46 +0000)]
insert missing .Ns
schwarze [Tue, 29 Jun 2021 14:04:16 +0000 (14:04 +0000)]
basic mdoc(7) macro cleanup; patch from me at EmilEngler dot com
patrick [Tue, 29 Jun 2021 12:51:18 +0000 (12:51 +0000)]
rktcphy(4)
patrick [Tue, 29 Jun 2021 12:46:36 +0000 (12:46 +0000)]
When configuring the USB3 phy, try the OFW PHY API first, and if there's
no matching device, fall back to xhci(4)'s PHY configuration code.
ok kettenis@
patrick [Tue, 29 Jun 2021 12:43:33 +0000 (12:43 +0000)]
Enable rktcphy(4).
ok kettenis@
patrick [Tue, 29 Jun 2021 12:43:09 +0000 (12:43 +0000)]
Add rktcphy(4), a driver for the Type-C PHY controller found on the
Rockchip RK3399. While the PHY allows switching between combinations
of USB3 and DisplayPort, this driver enables only USB3 functionality.
This allows USB3 devices to show up on machines where previously only
USB2 devices showed up. Driver was taken from FreeBSD and adjusted to
fit into our code base.
ok kettenis@
kettenis [Tue, 29 Jun 2021 12:22:39 +0000 (12:22 +0000)]
The way we boot OpenBSD, there is no need to play the hart lottery.
This is essentially a remnant of early RISC-V, which used the Berkely
Boot Loader. Modern RISC-V firmware makes sure only one hart is enabled
and offsers SBI calls to start the other harts.
claudio [Tue, 29 Jun 2021 07:55:29 +0000 (07:55 +0000)]
Adjust unveil_find_cover() to return -1 if the root vnode is passed in.
This helps unveil_add_vnode() to properly re-evaluate unveils when
"/" is added to the list.
Because of this adjust unveil_covered() to check for the root as well
so that in that case the unveil uv is returned instead of NULL. Traversing
up from the root returns the root. This check is not really needed since
namei has its own root check and shortcuts for root vnodes.
OK semarie@
jsg [Tue, 29 Jun 2021 01:46:35 +0000 (01:46 +0000)]
remove arch ifdefs around drm.h include
ok deraadt@ kettenis@
jsg [Tue, 29 Jun 2021 01:42:14 +0000 (01:42 +0000)]
move some config lines to ensure drm.h is always created
ok deraadt@ kettenis@
schwarze [Mon, 28 Jun 2021 19:59:09 +0000 (19:59 +0000)]
delete the two pairs of extra blank lines from expected man(7) terminal
output that are no longer printed since man_term.c rev. 1.189
krw [Mon, 28 Jun 2021 19:50:30 +0000 (19:50 +0000)]
Add another epicycle to -A processing that ensures ONLY the
partition table is changed. Not the GPT header. Not the MBR. And
only write back as much partition table information as the header
claims to have room for.
At a minimum should make -A safer when operating on the Apple M1
GPT.
A major overhaul of this code is urgently needed before someone
sneezes too hard in its vicinity.
Feedback kettenis@ & ok deraadt@
schwarze [Mon, 28 Jun 2021 19:49:57 +0000 (19:49 +0000)]
In terminal output of man(7) documents, stop printing two extra blank
lines before the NAME section and before the page footer. While these
blank lines had a long tradition, they didn't really serve any purpose
and merely wasted screen real estate. Besides, this makes output from
man(7) more similar to output from mdoc(7).
This commit keeps mandoc compatible with groff-current,
where G. Branden Robinson committed the same change
on June 16 (groff commit
2278d6ed).
deraadt [Mon, 28 Jun 2021 18:53:10 +0000 (18:53 +0000)]
do not need .align 2 or 4 after .text, the ABI's .text will decide what
to do
ok kettenis
deraadt [Mon, 28 Jun 2021 18:52:26 +0000 (18:52 +0000)]
whitespace
tb [Mon, 28 Jun 2021 18:48:56 +0000 (18:48 +0000)]
Use the order action->sender == ctx->mode everywhere for consistency.
tb [Mon, 28 Jun 2021 18:42:17 +0000 (18:42 +0000)]
ctx->alert is not a boolean, so compare it explicitly against 0.
kettenis [Mon, 28 Jun 2021 18:38:17 +0000 (18:38 +0000)]
Fix assembly in #ifdef MULTIPROCESSOR case.
ok jsing@
kettenis [Mon, 28 Jun 2021 18:21:08 +0000 (18:21 +0000)]
Add speculation-blocking sequence after syscalls like we did for libc a while
ago. While there, fix the SYS_exit syscall. The syscall number is passed in
r12, not as the argument of the syscall instruction.
ok deraadt@
deraadt [Mon, 28 Jun 2021 15:45:15 +0000 (15:45 +0000)]
delete .align inside sigtramp stubs, as the stack alignment requirement
hasn't existed for many years, since the code was moved it into a unique page,
with trap sleds.
ok kettenis
tb [Mon, 28 Jun 2021 15:36:51 +0000 (15:36 +0000)]
The state machine now takes care of setting the legacy state,
so it is no longer necessary in to do this by hand in various
places of the code interfacing with the legacy stack.
ok jsing
tb [Mon, 28 Jun 2021 15:35:14 +0000 (15:35 +0000)]
Expand info callback support for TLSv1.3
During the TLSv1.3 handshake, update the legacy state and call the
info callback at the appropriate moment. This is done by mapping
the TLSv1.3 states to the states in the old state machine whenever
that is possible. The callbacks are called at the beginning and end
of the handshake, and just before the state machine advances.
This should fix a periodic warning in logs of tor relays about a
variable that wasn't set although it should have been.
input/ok jsing, ok inoguchi (early version)
stsp [Mon, 28 Jun 2021 14:35:42 +0000 (14:35 +0000)]
Have tcpdump split the 802.11 sequence number field into its sequence number
and fragment number components instead of printing the whole field in decimal.
ok sthen@ kn@ jca@
espie [Mon, 28 Jun 2021 14:17:01 +0000 (14:17 +0000)]
placeholder for later
tb [Mon, 28 Jun 2021 14:01:38 +0000 (14:01 +0000)]
Garbage collect loop index i which is no longer used after usage tweak.
jca [Mon, 28 Jun 2021 13:47:46 +0000 (13:47 +0000)]
Fix base-gcc -Wno-error=uninitialized
base-gcc always errored out when -Werror was passed and -Wuninitialized
triggered, even when -Wno-error=uninitialized was passed.
Deemed correct by Miod
espie [Mon, 28 Jun 2021 11:25:14 +0000 (11:25 +0000)]
remove old "paranoid" option, I'm pretty sure nobody uses it.
refactor the code into figuring out simple updates: if we don't have
any @execs but just @tags, we can probably do something simpler wrt
temporary files and temporary filenames, which should speed up texlive
updates significantly.
(the tempfile code is not there yet, just the check for safe updates)
mpi [Mon, 28 Jun 2021 11:19:01 +0000 (11:19 +0000)]
Make anonymous object reference counting independant from the KERNEL_LOCK().
- Use atomic operations for increment/decrement
- Rewrite the loop from uao_swap_off() to only keep a reference to the
next item in the list.
ok jmatthew@
mpi [Mon, 28 Jun 2021 11:04:14 +0000 (11:04 +0000)]
Enable dt(4).
ok kettenis@
kettenis [Mon, 28 Jun 2021 09:35:09 +0000 (09:35 +0000)]
Implement copyin32().
ok deraadt@
bluhm [Mon, 28 Jun 2021 08:55:06 +0000 (08:55 +0000)]
Also show the time spent in userland when analyzing the kernel stack
in flame graph. Only when both kernel and userland are displayed,
the whole picture of system activity becomes clear. Fixes a parsing
bug in the flame graph tool where userland time was interpreted as
invalid kernel stack.
OK kn@
kettenis [Sun, 27 Jun 2021 21:39:55 +0000 (21:39 +0000)]
Make sure __bss_start is aligned on an 8-byte boundary. This makes sure
zeroing out .bss doesn't overrun and overwrite the ELF symbol table.
ok patrick@
kettenis [Sun, 27 Jun 2021 20:36:57 +0000 (20:36 +0000)]
Using the MI mplock should be fine on riscv64.
jsing [Sun, 27 Jun 2021 19:23:51 +0000 (19:23 +0000)]
Track the sigalgs used by ourselves and our peer.
Move the sigalg pointer from SSL_HANDSHAKE_TLS13 to SSL_HANDSHAKE, naming
it our_sigalg, adding an equivalent peer_sigalg. Adjust the TLSv1.3 code
that records our signature algorithm. Add code to record the signature
algorithm used by our peer.
Needed for upcoming API additions.
ok tb@
jsing [Sun, 27 Jun 2021 19:16:59 +0000 (19:16 +0000)]
Have ssl3_send_client_verify() pass *pkey to called functions.
ssl3_send_client_verify() already has a pointer to the EVP_PKEY for the
certificate - pass this as an argument to the functions that it calls,
rather than duplicating code/variable declarations.
jsing [Sun, 27 Jun 2021 18:15:35 +0000 (18:15 +0000)]
Change ssl_sigalgs_from_value() to perform sigalg list selection.
Rather that passing in a sigalg list at every call site, pass in the
appropriate TLS version and have ssl_sigalgs_from_value() perform the
sigalg list selection itself. This allows the sigalg lists to be made
internal to the sigalgs code.
ok tb@
jsing [Sun, 27 Jun 2021 18:09:07 +0000 (18:09 +0000)]
Rename ssl_sigalg() to ssl_sigalg_from_value().
This makes the code more self-documenting and avoids the ambiguity between
ssl_sigalg the struct and ssl_sigalg the function.
ok tb@
jsing [Sun, 27 Jun 2021 17:59:17 +0000 (17:59 +0000)]
Change ssl_sigalgs_build() to perform sigalg list selection.
Rather that doing sigalg list selection at every call site, pass in the
appropriate TLS version and have ssl_sigalgs_build() perform the sigalg
list selection itself. This reduces code duplication, simplifies the
calling code and is the first step towards internalising the sigalg lists.
ok tb@
schwarze [Sun, 27 Jun 2021 17:57:13 +0000 (17:57 +0000)]
add a style message about overlong text lines,
trying very hard to avoid false positives,
not at all trying to catch as many cases as possible;
feature originally suggested by tb@,
OK tb@ kn@ jmc@
jsing [Sun, 27 Jun 2021 17:50:06 +0000 (17:50 +0000)]
Tidy some comments and simplify some code.
ok tb@
jsing [Sun, 27 Jun 2021 17:45:16 +0000 (17:45 +0000)]
Keep sigalg initialiser order consistent - key type, then hash.
This matches the order that sigalgs are specified in.
ok tb@
jsing [Sun, 27 Jun 2021 17:13:23 +0000 (17:13 +0000)]
Add test coverage for TLSv1.3 client hellos.
This is a little bit clunky due to the number of things that vary (largely
thanks to middlebox compatibility mode, along with the versions and key
share extensions), however it works and can be improved at a later date.
jsing [Sun, 27 Jun 2021 16:55:46 +0000 (16:55 +0000)]
Add test coverage for DTLSv1.2 client hellos.
jsing [Sun, 27 Jun 2021 16:54:55 +0000 (16:54 +0000)]
Improve test coverage for SSL_OP_NO_DTLSv1.
jsing [Sun, 27 Jun 2021 16:54:14 +0000 (16:54 +0000)]
Correct handling of SSL_OP_NO_DTLSv1.
When converting to TLS flags, we need to also include SSL_OP_NO_TLSv1,
otherwise the TLS equivalent of SSL_OP_NO_DTLSv1 is TLSv1.0 only, which
does not work so well when we try to switch back to DTLS versions.
jsing [Sun, 27 Jun 2021 16:40:25 +0000 (16:40 +0000)]
Teach hexdump() how to identify differing bytes.
This allows differences between the received data and the test data to be
more readily identified.
jsing [Sun, 27 Jun 2021 16:36:53 +0000 (16:36 +0000)]
More appropriately set cipher_list_len when AES acceleration is available.
jsing [Sun, 27 Jun 2021 16:33:30 +0000 (16:33 +0000)]
Tweak some data types and sprinkle some const.
schwarze [Sun, 27 Jun 2021 15:53:33 +0000 (15:53 +0000)]
In addition to 2-byte and 3-byte UTF-8 sequences, correctly identify all
4-byte UTF-8 sequences and not just some of them, to keep them together
and avoid passing them on byte by byte, helping tools like tmux(1).
While here, also do all the range tests with < and > rather than &
for uniformity and readability, and add some comments.
Input and OK jca@ and nicm@.
Soeren at Soeren dash Tempel dot net originally reported the bug
and provided an incomplete patch that was used as a starting point,
and he also tested this final patch.
kettenis [Sun, 27 Jun 2021 15:02:25 +0000 (15:02 +0000)]
Add Hart State Management functions. These will be needed to spin up
the secondary cores. From FreeBSD.
ok mlarkin@
jsg [Sun, 27 Jun 2021 04:52:01 +0000 (04:52 +0000)]
reuse armv7 installboot for riscv64
ok deraadt@
visa [Sun, 27 Jun 2021 04:33:40 +0000 (04:33 +0000)]
Create DMA maps with 64-bit capability when appropriate.
OK kettenis@
visa [Sun, 27 Jun 2021 04:32:31 +0000 (04:32 +0000)]
Use config register to determine if 64-bit DMA is available.
Suggested by and OK kettenis@
jsg [Sun, 27 Jun 2021 01:58:51 +0000 (01:58 +0000)]
match on sifive,fu540-c000-gem
used by the hifive unmatched device tree in mainline linux and u-boot
ok visa@
jmc [Sat, 26 Jun 2021 18:03:45 +0000 (18:03 +0000)]
make usage less chatty; ok mlarkin
jmc [Sat, 26 Jun 2021 18:02:48 +0000 (18:02 +0000)]
make SYNOPSIS match usage; ok ajacoutot
kettenis [Sat, 26 Jun 2021 17:38:40 +0000 (17:38 +0000)]
For some reason the riscv64 locore.S ended up with the copyright license
from the arm64 locore.S. But the code was clearly copied from FreeBSD's
riscv64 locore.S. The license is the same, but the author/attribution isn't.
Fix this.
ok deraadt@
tb [Sat, 26 Jun 2021 17:36:28 +0000 (17:36 +0000)]
Fix .Xr order. From mandoc -Tlint.
deraadt [Sat, 26 Jun 2021 15:42:58 +0000 (15:42 +0000)]
delete extra explanations in the usage: messages which are described
far better in the manual pages
ok jmc
kettenis [Sat, 26 Jun 2021 14:50:25 +0000 (14:50 +0000)]
Make lazy binding work on riscv64.
prompted by deraadt@
kettenis [Sat, 26 Jun 2021 14:47:54 +0000 (14:47 +0000)]
Build ld.so with --march=rv64imac on riscv64 to be absolutely sure that
ld.so doesn't use the FP registers.
ok deraadt@
kettenis [Sat, 26 Jun 2021 14:46:48 +0000 (14:46 +0000)]
Use AFLAGS when building syscall stubs. Drop AINC wich isn't used.
ok deraadt@
visa [Sat, 26 Jun 2021 10:47:59 +0000 (10:47 +0000)]
cad: Implement 64-bit DMA mode
This lets the driver utilize 64-bit DMA on hardware that supports it.
Currently, riscv64 does not constrain DMA-reachable memory to the 32-bit
range. This caused memory errors with cad(4) on machines that have RAM
above 4GB in the physical address space.
Prompted by Mickael Torres
OK kettenis@
kettenis [Sat, 26 Jun 2021 09:24:51 +0000 (09:24 +0000)]
Add riscv64 support. From Mickael Torres.
ok matthieu@, jsg@