Re: [PATCH] Typo in hastd.8 man page

2019-12-21 Thread Kirk McKusick
> Date: Sat, 21 Dec 2019 12:03:47 -0800 > From: Steve Kargl > To: freebsd-current@freebsd.org > Subject: [PATCH] Typo in hastd.8 man page > > Path should explain the issue. > > Index: hastd.8 > === > --- hastd.8 (revision 355983)

Re: drm-current-kmod panics

2019-12-21 Thread Cy Schubert
In message , Jeff Roberson wri tes: > On Thu, 19 Dec 2019, Hans Petter Selasky wrote: > > > On 2019-12-19 19:40, Cy Schubert wrote: > >> In message , Hans Petter > >> Sela > >> sky writes: > >>> On 2019-12-19 17:50, Cy Schubert wrote: > Has anyone else had these since Dec 9? > > <4

r355978 OK (was: SVN r355732 breaks DRM)

2019-12-21 Thread Graham Perrin
On 18/12/2019 10:21, Evilham wrote: On dc., des. 18 2019, Graham Perrin wrote: On 14/12/2019 01:30, Warner Losh wrote:  > A fix is in progress. Thank you. r355860 drm-legacy-kmod lines 70–81: the same issue, yes? FWIW: https://github.com/FreeBSDDesktop/kms-

[PATCH] Typo in hastd.8 man page

2019-12-21 Thread Steve Kargl
Path should explain the issue. Index: hastd.8 === --- hastd.8 (revision 355983) +++ hastd.8 (working copy) @@ -44,7 +44,7 @@ daemon is responsible for managing highly available GEOM providers. .Pp .Nm -allows the transpaent

Current r355939 + drm-current-kmod 4.16g20191217 compiles and runs

2019-12-21 Thread Thomas Laus
After about one week of problems, I was able to successfully compile and start DRM on 3 computers. My hardware Atom D510, Intel i5 Skylake and an Intel Core2-Duo laptop. I had to rm -rf /usr/obj/* on all of them however, to get a successful compile. Thanks Tom -- Public Keys: PGP KeyID = 0x5F