OpenBSD cvs log

created 2019-09-18T16:54:13Z
begin 2019-09-09T00:00:00Z
end 2019-09-10T00:00:00Z
path src/sys
commits 11

date 2019-09-09T01:35:43Z
author jsg
files src/sys/dev/pci/drm/drm_fb_helper.c log diff annotate
message When no display outputs are connected on boot linux 4.19 drm relies on
deferred setup to handle the console framebuffer where as linux 4.4 drm
created a 1024x768 console framebuffer in this situation.

As we only handle setting up rasops and wsdisplay on attach go back to
the old behaviour for now so a display can be connected after booting
with none attached to interact with the console.

This partly reverts linux commit
drm/fb-helper: Support deferred setup
ca91a2758fcef6635626993557dd51cfbb6dd134

Reported and tested by Marcus MERIGHI.
Tested by and ok kettenis@

date 2019-09-09T01:37:27Z
author krw
files src/sys/scsi/st.c log diff annotate
message Tweak some comments to be useful. Sort switch cases into
numerical order. Move bit of logic before calling
st_unmount() into st_unmount().

date 2019-09-09T02:57:20Z
author jmatthew
files src/sys/dev/pci/if_mcx.c log diff annotate
message Specify the right opcode when trying to set the Interface Step Sequence ID.
Newer firmware (version 14.25) doesn't allow the driver to create TIS
contexts without setting the ISSI, but earlier firmware doesn't seem to care.
Big thanks to Xiaofeng Liu from Mellanox support who identified the problem.

fixes problems first reported by patrick@

date 2019-09-09T09:38:04Z
author dlg
files src/sys/dev/pci/mfii.c log diff annotate
message revert back to using 0x6c for the reply post index register.

this was mistakenly committed as part of the powerdown hook stuff,
and caused "older" chips like SAS2208s to get stuck in biowait.

reported by Mischa and hrvoje popovski
discussed with jmatthew@ and alex wilson.
fix tested by me on a SAS3508 and SAS2208

date 2019-09-09T18:02:12Z
author krw
files src/sys/scsi/st.c log diff annotate
message Lots of st->flags checking in a mix of old school and ISSET() makes
code harder to read. Switch to ISSET() where obvious.

No change to executable.

date 2019-09-09T18:25:47Z
author krw
files src/sys/scsi/st.c log diff annotate
message Lots of st->flags bit clearing in a mix of old school and CLR() makes
code harder to read. Switch to CLR().

No change to executable.

date 2019-09-09T18:59:20Z
author krw
files src/sys/scsi/st.c log diff annotate
message Continue bit twiddling tweaks. Use SET() with st->flags.

date 2019-09-09T20:00:27Z
author patrick
files src/sys/arch/arm64/conf/GENERIC log diff annotate
src/sys/arch/arm64/conf/RAMDISK log diff annotate
src/sys/dev/fdt/imxsrc.c log diff annotate
message Attach imxsrc(4) early and raise its priority to make sure it beats
syscon(4).

ok kettenis@

date 2019-09-09T20:00:51Z
author patrick
files src/sys/dev/fdt/imxsrc.c log diff annotate
message Update the bindings for imxsrc(4), since they changed when they were
upstreamed.

ok kettenis@

date 2019-09-09T20:02:26Z
author bluhm
files src/sys/sys/acct.h log diff annotate
src/sys/uvm/uvm_map.c log diff annotate
message Inform about system call memory write protection and stack mapping
violations in system accounting. This will help to find missbehaving
programs and possible attacks. The flags bit field is full, so
recycle the PDP-11 compatibility on VAX. lastcomm(1) prints the
AMAP flag as 'M'. daily(8) prints a list of affected processes.
OK deraadt@

date 2019-09-09T23:28:41Z
author krw
files src/sys/scsi/st.c log diff annotate
message SET/CLR/ISSET all at once for the far less numerous link->flags.