Re: sparc64 ldomctl(8) fix

2019-07-05 Thread Klemens Nanni
On Sat, Jul 06, 2019 at 01:23:40AM +0200, Mark Kettenis wrote: > > Date: Sat, 6 Jul 2019 01:15:59 +0200 > > From: Klemens Nanni > > > > Still lists all domains on my T5240 with this change. > > I hope you mean all ldom configurations here ;). He, yes :) # ldomctl list

Re: sparc64 ldomctl(8) fix

2019-07-05 Thread Mark Kettenis
> Date: Sat, 6 Jul 2019 01:15:59 +0200 > From: Klemens Nanni > > Still lists all domains on my T5240 with this change. I hope you mean all ldom configurations here ;).

Re: sparc64 ldomctl(8) fix

2019-07-05 Thread Klemens Nanni
Still lists all domains on my T5240 with this change.

sparc64 ldomctl(8) fix

2019-07-05 Thread Mark Kettenis
The diff below fixes interction between ldomctl(8) and the firmware on a SPARC T4 system that I have access to. To make sure that this doesn't break other machines it would be good if people could test this on a few more ldoms-capable sparc64 machines. To test just build ldomctl with this patch,

Re: vmctl: unnecessary space in usage

2019-07-05 Thread Jason McIntyre
On Fri, Jul 05, 2019 at 10:55:30PM +0200, Alessandro Gallo wrote: > Hi, > > There seems to be an extra space in the vmctl command usage. The > following diff removes it: > fixed, thanks. jmc > Index: main.c > === > RCS file:

vmctl: unnecessary space in usage

2019-07-05 Thread Alessandro Gallo
Hi, There seems to be an extra space in the vmctl command usage. The following diff removes it: Index: main.c === RCS file: /cvs/src/usr.sbin/vmctl/main.c,v retrieving revision 1.56 diff -u -p -u -p -r1.56 main.c --- main.c 29

Re: watchdog: use timeout_add_sec(9)

2019-07-05 Thread Klemens Nanni
On Fri, Jul 05, 2019 at 04:14:44PM -0500, Scott Cheloha wrote: > This looks incorrect. If the watchdog period is odd you're truncating > the timeout by one second. It is, but I (carelessly) looked over this detail. > If you convert to milliseconds it's fine to divide by 2, so I suggest > you do

Re: watchdog: use timeout_add_sec(9)

2019-07-05 Thread Scott Cheloha
On Fri, Jul 05, 2019 at 03:05:24PM +0200, Klemens Nanni wrote: > Simple reduction here as done in many other places, tested on an ARMv7 > BeagleBone Black with > > omdog0 at simplebus0 rev 0.1 > > # sysctl kern.watchdog.period=3 > # sysctl kern.watchdog.auto=0 > > which

Re: mg(1) evaluate multi-argument commands

2019-07-05 Thread Mark Lumsden
I should add, I meant to put checks in for the calls to strlcpy and strlcat, but was pushed for time and forgot.. but of course they would be put in.

mg(1) evaluate multi-argument commands

2019-07-05 Thread Mark Lumsden
I was finding it a bit tedious with long evaluation buffers so I wrote a function that would translate these three (or more) lines: find-file a.txt find-file b.txt find-file c.txt into this one line: (find-file a.txt b.txt c.txt) There are a few commands that can be used like this: insert,

Re: port NetBSD libc tests

2019-07-05 Thread Alexander Bluhm
On Mon, Jul 01, 2019 at 11:43:17AM -0300, Martin Pieuchot wrote: > What's your goal? Are you trying to find bugs by increasing the amount > of code coverage? Having coverage for system calls is a good thing. Checking where the differences between NetBSD and OpenBSD are, is also good. > I don't

Re: lock(1): make -n and -t options mutually exclusive

2019-07-05 Thread Klemens Nanni
On Fri, Jul 05, 2019 at 08:57:08AM -0500, Scott Cheloha wrote: > So I should change the usage but not the manpage synopsis? Or neither > should change but I should document that the options are incompatible? Neither should change. > Is this any better? OK, although I would've said "mutually

Re: lock(1): make -n and -t options mutually exclusive

2019-07-05 Thread Scott Cheloha
On Thu, Jul 04, 2019 at 11:35:59PM -0600, Theo de Raadt wrote: > Klemens Nanni wrote: > > > On Thu, Jul 04, 2019 at 12:43:21PM -0500, Scott Cheloha wrote: > > > It doesn't make sense to allow the user to simultaneously set -n > > > (never time out) and also set -t timeout (release the terminal

watchdog: use timeout_add_sec(9)

2019-07-05 Thread Klemens Nanni
Simple reduction here as done in many other places, tested on an ARMv7 BeagleBone Black with omdog0 at simplebus0 rev 0.1 # sysctl kern.watchdog.period=3 # sysctl kern.watchdog.auto=0 which reliably reboots the system after the specified amount of time. OK? Index:

Re: drm(4), multi-threaded task queues and barriers

2019-07-05 Thread Jonathan Gray
On Fri, Jul 05, 2019 at 12:20:20PM +0200, Mark Kettenis wrote: > > Date: Fri, 5 Jul 2019 14:20:40 +1000 > > From: Jonathan Gray > > > > On Wed, Jun 12, 2019 at 09:15:36AM +0200, Mark Kettenis wrote: > > > > Date: Wed, 12 Jun 2019 17:04:10 +1000 > > > > From: Jonathan Gray > > > > > > > > On

Re: drm(4), multi-threaded task queues and barriers

2019-07-05 Thread Mark Kettenis
> Date: Fri, 5 Jul 2019 14:20:40 +1000 > From: Jonathan Gray > > On Wed, Jun 12, 2019 at 09:15:36AM +0200, Mark Kettenis wrote: > > > Date: Wed, 12 Jun 2019 17:04:10 +1000 > > > From: Jonathan Gray > > > > > > On Tue, Jun 11, 2019 at 09:10:46PM +0200, Mark Kettenis wrote: > > > > The drm(4)

uvideo(4): support IR video format

2019-07-05 Thread Patrick Wildt
Hi, the second camrea on my Lenovo X395 is an "IR" camera that produces some greyscale picture. video(1) doesn't support that format, but with this patch I can use $ ffmpeg -f v4l2 -i /dev/video1 test.mp4 $ mplayer test.mp4 to record and show the video correctly. Patrick diff --git

Re: pf: use proper interface for route-to when it is used with sticky-address

2019-07-05 Thread YASUOKA Masahiko
Hi, Previous diff made src-node have a reference for the kif. My colleague pointed out that incrementing the reference count of the kif is required. ok? Fix previous commit which made src-node have a reference for the kif. Src-node should use the reference counter since it might live longer

remove duplicate code

2019-07-05 Thread Kevin Lo
ok? Index: sys/dev/usb/if_axe.c === RCS file: /cvs/src/sys/dev/usb/if_axe.c,v retrieving revision 1.138 diff -u -p -u -p -r1.138 if_axe.c --- sys/dev/usb/if_axe.c22 Jan 2017 10:17:39 - 1.138 +++ sys/dev/usb/if_axe.c

Re: fix pfctl regress on armv7

2019-07-05 Thread Claudio Jeker
On Thu, Jul 04, 2019 at 10:03:20PM +0200, Moritz Buhl wrote: > Hi, > > due to the pfctl regression tests failing on armv7 I noticed that the > yyerror function is having the usual format attributes. This lead to > garbage in error messages on armv7. I added the directives and then > adjusted the

Re: fix format strings in relayd

2019-07-05 Thread Claudio Jeker
On Thu, Jul 04, 2019 at 10:15:54PM +0200, Moritz Buhl wrote: > Hi, > > as promised a patch to relayd to enable formatting warnings for yyerror. OK claudio@ > Greetings, > Moritz Buhl > > Index: usr.sbin/relayd/parse.y > === > RCS