envy(4): *sleep(9) -> *sleep_nsec(9)

ok? Index: envy.c === RCS file: /cvs/src/sys/dev/pci/envy.c,v retrieving revision 1.79 diff -u -p -r1.79 envy.c --- envy.c 9 May 2019 05:17:45 - 1.79 +++ envy.c 23 Nov 2019 00:40:53 - @@ -2218,7 +2218,8 @@ envy

cardbus(4): tsleep -> tsleep_nsec(9)

ok? Index: cardbus.c === RCS file: /cvs/src/sys/dev/cardbus/cardbus.c,v retrieving revision 1.51 diff -u -p -r1.51 cardbus.c --- cardbus.c 28 Aug 2015 00:03:53 - 1.51 +++ cardbus.c 23 Nov 2019 00:31:11 - @@ -408,8 +40

pckbc(4): tsleep -> tsleep_nsec(9)

ok? Index: pckbc.c === RCS file: /cvs/src/sys/dev/ic/pckbc.c,v retrieving revision 1.52 diff -u -p -r1.52 pckbc.c --- pckbc.c 3 Jun 2019 16:46:49 - 1.52 +++ pckbc.c 23 Nov 2019 00:27:11 - @@ -931,7 +931,7 @@ pckb

onewire, owtemp(4): tsleep -> tsleep_nsec(9)

ok? Index: onewire.c === RCS file: /cvs/src/sys/dev/onewire/onewire.c,v retrieving revision 1.17 diff -u -p -r1.17 onewire.c --- onewire.c 3 Apr 2017 16:10:00 - 1.17 +++ onewire.c 23 Nov 2019 00:18:24 - @@ -39,7 +39,

misc. acpi(4): *sleep -> *sleep_nsec(9)

The acpi_event_wait() loop is tricky. I'm leaving it alone for now. Everything else here is straightforward, though. The acpiec(4) sleep is adjacent to a delay of 1 microsecond so I've chosen that to replace the current duration of 1 tick. ok? Index: acpi.c

Re: sysupgrade: Allow to use another directory for the sets

On 22/11/2019 16:38, Craig Skinner wrote: On Tue, 19 Nov 2019 10:35:56 + Stuart Henderson wrote: We are short on partitions, there is a hard limit (14+swap), disklabel auto defaults already use 9, and there need to be some free for typical user use (ports, dest for "make release", people o

Re: ix(4) need support for X553

On Thu, Nov 14, 2019, at 1:06 AM, Stuart Henderson wrote: *snip* > > I have an A2SDi-2C-HLN4F that I need to put in service soon (not so > bothered about the ix on this box, I'm using 4xSFP+ ixl, but giving it > a spin) - applying my merged diff (https://junkpile.org/ixgbe.diff2) > and adding PC

Re: sysupgrade: Allow to use another directory for the sets

On 2019/11/22 15:38, Craig Skinner wrote: > Could a similar /tmp/sysupgrade/ default directory suit most situations? My systems with MFS /tmp say no.

Re: sysupgrade: Allow to use another directory for the sets

I vote for this. On Fri, 22 Nov 2019 at 16:12, Craig Skinner wrote: > On Tue, 19 Nov 2019 10:35:56 + Stuart Henderson wrote: > > We are short on partitions, there is a hard limit (14+swap), disklabel > auto > > defaults already use 9, and there need to be some free for typical user > use >

Re: sysupgrade: Allow to use another directory for the sets

On Tue, 19 Nov 2019 10:35:56 + Stuart Henderson wrote: > We are short on partitions, there is a hard limit (14+swap), disklabel auto > defaults already use 9, and there need to be some free for typical user use > (ports, dest for "make release", people often want a separate /var/www and/or > /v