OpenBSD src changes summary for 2017-09-04 ==========================================
regress/sys sys/arch/octeon/dev sys/dev/acpi sys/dev/pci sys/dev/usb sys/net80211 usr.bin/ctfconv usr.bin/ssh usr.bin/tmux == regress =========================================================== 01/03 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/regress sys ~ nfs/Makefile ~ ffs/nfs/Makefile > Before mounting NFS, wait until mountd(8) has exported the directory. > Fixes a race in the test setup. > OK mpi@. (bluhm@) ~ net/pf_divert/Makefile ~ net/pf_divert/Packet.pm > Run divert-packet tests also for IPv6. (bluhm@) == sys =============================================================== 02/03 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys arch/octeon/dev ~ octmmc.c ~ octmmcreg.h > Let octmmc(4) attach on revision 7890 controller. (visa@) dev/acpi ~ acpibat.c > Don't require exactly 20 elements in the _BIX package if at least 20 > are returned since extras may be OEM-specific values we end up > ignoring anyway, such as on the Lenovo X1C 5th Gen which returns 21 > elements. > ok mpi (jcs@) dev/pci ~ if_iwn.c > Make sure iwn(4) firmware gets to see a beacon before we send an auth > request. > Otherwise, the Tx attempt can fail due to the firmware's built-in > regulatory > domain enforcement. > Because this code runs in interrrupt context we use a DELAY(). It's > currently > set to 3 times the beacon interval. This is a bit long as far as DELAYs go, > but since this driver runs state transitions in interrupt context there is > no better way for now. Lower delays weren't reliable enough in my testing. > Makes association work reliably for me on 5GHz. My original plan was to > only > add this hack for 5GHz but Holger Mikolon reported that it also helps on > 2GHz > channels with regulatory restrictions (e.g. 13), so do it always. > ok mpi@ (stsp@) dev/usb ~ xhci.c > Revert previous: "Fix a remaining length miscalculation in xhci(4)." > It made one of my machines get stuck during boot. (stsp@) net80211 ~ ieee80211_input.c > If a beacon is received in RUN state, reset the management timer. > Some wifi drivers send a probe request if the hardware reports "missed > beacon" > events. If the AP replies with a probe response it is still servicing us > and > there is no need to search for a new AP. However, the management timer was > not > reset if a beacon was received while in RUN state. So the interface > watchdog > always ended up putting the driver into SCAN state after a missed beacon > event, > even if the AP did respond to our probe request. Under some conditions this > bug would cause spurious disconnects. > Problem reported and fix tested by mlarkin@ > (Using the management timer in RUN state is a new convention. Before > support > for missed beacons was added, this timer was only used during the > association > sequence to handle APs which don't respond to our assoc requests and such.) > (stsp@) == usr.bin =========================================================== 03/03 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin ctfconv ~ dw.c > Fix typo in comment; ok mpi@ (anton@) ssh ~ ssh_config.5 > tweak previous; (jmc@) tmux ~ tmux.1 ~ window-copy.c > Move to current mouse position not last when clcking in copy mode; fixes > GitHub issue 1055. Also a man page fix from jmc. (nicm@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
