Re: Marvel Yukon Ultra II NIC badly supported by msk driver

Hi, Thanks for the patch. Unfortunately it made no difference, same issue and error message. Regards, Damien On Thu, Mar 15, 2018 at 02:27:09PM +0100, Martin Pieuchot wrote: On 28/02/18(Wed) 20:01, Damien Boureille wrote: Hi, I'm trying to install OpenBSD 6.2 on a Netgear RNDU2000 NAS. The

Re: shutdown(8): disallow "++minutes"

On Fri, 16 Mar 2018 14:23:29 -0500, Scott Cheloha wrote: > Because we increment the timearg pointer, shutdown(8) accepts > stuff like > > shutdown ++10 > > as strtonum(3) allows a single leading '+'. > > Not incrementing leaves the offset in a valid format for strtonum(3) > and disallows

shutdown(8): disallow "++minutes"

Because we increment the timearg pointer, shutdown(8) accepts stuff like shutdown ++10 as strtonum(3) allows a single leading '+'. Not incrementing leaves the offset in a valid format for strtonum(3) and disallows stuff like the above. While here: - time_t is 64-bit, so the maximum

Re: SA_RESETHAND race (or the mpv(1) hanging story)

On Fri, Mar 16, 2018 at 02:29:24PM +0100, Hiltjo Posthuma wrote: > On Thu, Mar 15, 2018 at 03:27:47PM +0100, Martin Pieuchot wrote: > > On 05/03/18(Mon) 21:26, Hiltjo Posthuma wrote: > > > > [...] > > > > I tried your patch on a source build of about 25 februari on amd64. I > > > > still > > > >

Re: SA_RESETHAND race (or the mpv(1) hanging story)

On Thu, Mar 15, 2018 at 03:27:47PM +0100, Martin Pieuchot wrote: > On 05/03/18(Mon) 21:26, Hiltjo Posthuma wrote: > > > [...] > > > I tried your patch on a source build of about 25 februari on amd64. I > > > still > > > notice mpv hanging when I try to close it or when the video ends. > >

[patch] 62.html

Same as the rejected patch for the temporary 63.html, but this time for a relevant page. --- 62.html.orig2018-03-16 14:17:49.0 +0100 +++ 62.html 2018-03-16 14:18:07.0 +0100 @@ -180,9 +180,9 @@ MiRA 802.11n TX rate scaling now supports devices with unequal

FPU ptrace and core dump support for armv7

This brings armv7 in line with arm64. ok? Index: arch/arm/arm/arm_machdep.c === RCS file: /cvs/src/sys/arch/arm/arm/arm_machdep.c,v retrieving revision 1.4 diff -u -p -r1.4 arm_machdep.c --- arch/arm/arm/arm_machdep.c 16 Jul 2016

[patch] 63.html

Typo fix for 802.11 driver man page links --- 63.html.orig2018-03-16 12:41:10.0 +0100 +++ 63.html 2018-03-16 12:42:36.0 +0100 @@ -181,9 +181,9 @@ MiRA 802.11n TX rate scaling now supports devices with unequal numbers of Tx and Rx streams. Fixes 11n

Re: envy: set base DMA pointers when DMA starts

> Date: Fri, 16 Mar 2018 09:00:48 +0100 > From: Alexandre Ratchov > > The allocm() functions are supposed to allocate memory and it's bad > style to access the hardware there. The diff moves the DMA base > pointers setup to the trigger_xxx() routines which start DMA. No >

Re: envy: fix suspend/resume

> Date: Fri, 16 Mar 2018 09:01:51 +0100 > From: Alexandre Ratchov > > The chip is in an undefined state after a suspend/resume cycle so > sound doesn't comme back. Most of the resume work is done in the > audio(4) layer, so, to fix suspend/resume we just need to reinitize > the

envy: fix suspend/resume

The chip is in an undefined state after a suspend/resume cycle so sound doesn't comme back. Most of the resume work is done in the audio(4) layer, so, to fix suspend/resume we just need to reinitize the device. OK? Index: envy.c ===

envy: set base DMA pointers when DMA starts

The allocm() functions are supposed to allocate memory and it's bad style to access the hardware there. The diff moves the DMA base pointers setup to the trigger_xxx() routines which start DMA. No behavior change. OK? Index: envy.c