Date: Mon, 11 Feb 2019 09:10:56 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: sgk@troutmask.apl.washington.edu Cc: Johannes Lundberg <johalun0@gmail.com>, freebsd-current@freebsd.org Subject: Re: drm2 removed? Message-ID: <201902111710.x1BHAuvL071772@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20190211164051.GA41734@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, Feb 11, 2019 at 04:33:24PM +0000, Johannes Lundberg wrote: > > > > On 2/11/19 4:23 PM, Niclas Zeising wrote: > > > On 2/11/19 5:20 PM, 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. :( > > >> > > > > > > The code is still in base, but disabled by default.? I have to have a > > > look at this, but it might take a couple of days before we have a fix. > > > Regards > > > > Commit from 12 days ago and we get the news now... Any progress on the > > CI for drm modules? > > > > The commit ends with > > In collaboarion with: pho > Discussed with: emaste > Reviewed by: markj > MFC after: 2 weeks > Sponsored by: The FreeBSD Foundation > Differential revision: https://reviews.freebsd.org/D18894 > > No exp-run over ports. You'll likely see more reports when > the indicated MFC occurs in a day or two. If this breaks drm2, it must not be MFC'ed until that breakage is fixed, and I am sure kib knows that. I doubt there was any intent to brek drm2, it seems to have been over looked, and yet another reason to not unhook this from the builds in ^head. Rod <RE Thanks, -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201902111710.x1BHAuvL071772>