Date: Tue, 19 Feb 2019 11:18:07 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Johannes Lundberg <johalun0@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, freebsd-current@freebsd.org Subject: Re: What is evdev and autoloading? Message-ID: <20190219191807.GA2941@troutmask.apl.washington.edu> In-Reply-To: <b5972449-4b83-6f9b-fc17-7d7309ff6461@gmail.com> References: <201902181650.x1IGoRsZ006131@pdx.rh.CN85.dnsmgr.net> <11a49d72-3158-1b9a-f933-6702d8f5c238@nomadlogic.org> <362D8283-0B7D-402F-99CD-657021597955@cschubert.com> <20190219173554.GA1066@troutmask.apl.washington.edu> <b5972449-4b83-6f9b-fc17-7d7309ff6461@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 19, 2019 at 06:59:26PM +0000, Johannes Lundberg wrote: > > On 2/19/19 5:35 PM, Steve Kargl wrote: >> On Tue, Feb 19, 2019 at 08:17:48AM -0800, Cy Schubert wrote: >>> >>> Drm2 is not required. My current laptop is 5 years old, an HD3000. The previous one is 13 years old, i915. Both work perfectly with drm-current on 13-current. Franky, I don't see what the fuss is about. >>> >>> >> My Dell Latitude D530 running i386 freebsd, which used the >> i915kms.ko now locks up solid with drm-legacy-kmod. The PAE vs >> non-PAE i386/conf/pmap.h merger in r342567 broke drm-legacy-kmod. >> It seems that Niclas has provided a patch that fixes the building >> of drm-legacy-kmod. >> >> Doing a bisection on /usr/src commits is fairly slow as it >> takes a day to build world/kernel and the minimum set of ports >> need to fire up Xorg. r343543 and earlier appear to work fine >> with drm-legacy-kmod. > > So it's not only a build error, it's also a runtime bug that would have > happened even with drm2 in base? Hmm.. It appears that that's the case. The likely candidates are r343564(+65 for missing header), r343566, and r343567. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190219191807.GA2941>