Date: Mon, 11 Feb 2019 21:01:55 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current@freebsd.org Subject: Re: drm2 removed? Message-ID: <7eec9231-de47-b766-28ea-da72fbbf6c5c@gmail.com> In-Reply-To: <20190211204245.GA43956@troutmask.apl.washington.edu> References: <20190211161205.GB41262@troutmask.apl.washington.edu> <20190211162020.GA41438@troutmask.apl.washington.edu> <eabc11bc-ae86-1c20-dd4c-0a1bd4677f51@gmail.com> <20190211204245.GA43956@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/02/2019 20:42, Steve Kargl wrote: > On Mon, Feb 11, 2019 at 08:40:01PM +0000, Graham Perrin wrote: > >> On 11/02/2019 16:20, Steve Kargl wrote: >> >>> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: >>> >>>> Anyone have any idea which recent change broke the >>>> drm-legacy-kmod port. This is why I raised an issue >>>> with removal of drm2 from src/sys. How is suppose >>>> to be fixed? >>> >>> It was r343567. The merging of PAE and NO PAE pmap.h >>> by kib removed all of the missing macros. :( >> >> I found no trouble building drm-legacy-kmod with e.g. r343931. >> >> Just curious, does the breakage occur in only some situations? > > Are you building on i386 or x86_64? $ uname -a FreeBSD momh167-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT r343931 GENERIC-NODEBUG amd64 $ HP EliteBook 8570p. drm-kmod prefers drm-current-kmod but that nearly always fails for me, so I prefer legacy.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7eec9231-de47-b766-28ea-da72fbbf6c5c>