OpenBSD cvs log

created 2021-10-10T01:47:54Z
begin 2021-10-04T00:00:00Z
end 2021-10-05T00:00:00Z
path src/sys
commits 6

date 2021-10-04T01:29:57Z
author kevlo
files src/sys/dev/microcode/rsu/microcode.h log diff annotate
src/sys/dev/microcode/rsu/rsu-license log diff annotate
src/sys/dev/microcode/rtwn/microcode.h log diff annotate
src/sys/dev/microcode/rtwn/rtwn-license log diff annotate
src/sys/dev/microcode/urtwn/microcode.h log diff annotate
src/sys/dev/microcode/urtwn/urtwn-license log diff annotate
message Permission from Realtek to include wireless firmwares

After deraadt@ explained why the Realtek firmware cannot be put into our tree,
I reached out to Realtek to explain the situation.

According to the LICENCE.rtlwifi_firmware.txt [1], the rules permitted adding
their non-open-source firmware into open source operating systems but such
an addition (ironically) makes that open source operating system not entirely
open source. Realtek understood the irony, and change the license.

Thanks to Realtek for this change which lets us put the firmware .h file
into our tree, this means Realtek wireless will work without requiring
a firmware download (which is difficult over a non-working Realtek network :)

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.rtlwifi_firmware.txt?id=0f863ff1b388ad5b0f7d25decdbb642#n22

ok deraadt@

date 2021-10-04T01:33:42Z
author kevlo
files src/sys/dev/microcode/Makefile log diff annotate
src/sys/dev/microcode/rsu/Makefile log diff annotate
src/sys/dev/microcode/rsu/build.c log diff annotate
src/sys/dev/microcode/rtwn/Makefile log diff annotate
src/sys/dev/microcode/rtwn/build.c log diff annotate
src/sys/dev/microcode/urtwn/Makefile log diff annotate
src/sys/dev/microcode/urtwn/build.c log diff annotate
src/sys/dev/pci/if_rtwn.c log diff annotate
src/sys/dev/usb/if_rsu.c log diff annotate
src/sys/dev/usb/if_urtwn.c log diff annotate
message Build firmware for rsu(4), rtwn(4), and urtwn(4).
We have to install the files with new filenames (removal of "fw" from each of
the filenames) and change the driver to use the new filenames,
such that the package becomes irrelevant.

Discussed with deraadt@ and sthen@

ok deraadt@

date 2021-10-04T08:11:02Z
author claudio
files src/sys/kern/vfs_vops.c log diff annotate
src/sys/sys/vnode.h log diff annotate
src/sys/ufs/ext2fs/ext2fs_vfsops.c log diff annotate
src/sys/ufs/ffs/ffs_vfsops.c log diff annotate
message Use the fact the vnodes are locked when operations are inflight.
Remove the v_inflight member and alter the ffs and ext2fs sync code to
track inflight by checking if the node is locked or not (which it already
did before but for a different reason).
OK mpi@

date 2021-10-04T08:48:12Z
author claudio
files src/sys/kern/kern_sig.c log diff annotate
message Simplify sys___thrsigdivert a bit. cursig() always moves the pending signal
to p_siglist and so there is no need to check ps_siglist for the signal.
OK mpi@

date 2021-10-04T17:02:21Z
author deraadt
files src/sys/arch/i386/conf/RAMDISK_CD log diff annotate
message grow i386 media for new realtek firmwares

date 2021-10-04T19:04:12Z
author kettenis
files src/sys/dev/fdt/mvkpcie.c log diff annotate
message Allegedly a "Marvell Armada 3700 Functional Errata, Guidelines, and
Restrictions" document exists that discusses an errata #251 in section
"3.12 PCIe Completion Timeout" and suggests that setting the DIS_ORD_CHK
flag in the Debug Mux Control register is necessary as a workaround:

https://lore.kernel.org/linux-pci/[email protected]

This workaround is still being discussed by the Linux developers, but it
does fix an issue I am seeing with athn(4), where an external abort
happens under load. So apply this workaround since its potential side
effects seem to be significantly less severe than provoking an
external abort that hangs the machine.

ok patrick@