OpenBSD cvs log

created 2019-05-08T04:09:02Z
begin 2017-12-20T00:00:00Z
end 2017-12-21T00:00:00Z
path src/sys
commits 4

date 2017-12-20T02:02:31Z
author krw
files src/sys/dev/softraid.c log diff annotate
message Add a sanity check on the number of chunks being
assembled into a volume, to enure the on-disk
metadata and the in-memory metadata agree.

date 2017-12-20T11:08:44Z
author mpi
files src/sys/arch/amd64/amd64/Attic/mutex.c log diff annotate
src/sys/arch/amd64/conf/files.amd64 log diff annotate
src/sys/arch/i386/conf/files.i386 log diff annotate
src/sys/arch/i386/i386/locore.s log diff annotate
src/sys/arch/i386/i386/Attic/mutex.c log diff annotate
message Switch x86 architectures to the common C mutex implementation.

This is a step towards MI mutexes.

ok kettenis@

date 2017-12-20T11:22:29Z
author mpi
files src/sys/arch/alpha/alpha/Attic/mutex.c log diff annotate
src/sys/arch/arm64/arm64/Attic/arm64_mutex.c log diff annotate
src/sys/arch/mips64/mips64/Attic/mutex.c log diff annotate
src/sys/arch/powerpc/powerpc/Attic/mutex.c log diff annotate
message Sync C mutex implementations.

ok kettenis@

date 2017-12-20T18:20:59Z
author stsp
files src/sys/dev/pci/if_iwn.c log diff annotate
message Two background scan fixes for iwn(4) (4965 devices only):

1) Use only one antenna while scanning on 5GHz. Fixes very low RSSI values.

2) During a background scan while associated to a 5GHz AP, send probe
requests on 2GHz channels with an OFDM rate (6Mbps) because the buggy
firmware does not like sending with a CCK rate (1Mbps) in this state.
CCK rates are not valid for 5GHz, which could explain this firmware bug.

Taken from FreeBSD r222679.

jca@ tested and confirmed the first problem but lacks a 5GHz access point to
associate to and test the second one with.
I am going to *blindly trust* FreeBSD on the second one! It is not a big deal
if it doesn't actually apply to our firmware version as the change itself is
rather inconsequential in practice. And 4965 hardware is quite rare nowadays.

ok jca@