Date: Tue, 27 Feb 2018 11:51:30 +0300 From: Greg V <greg@unrelenting.technology> To: Pete Wright <pete@nomadlogic.org>, Mylan Connolly <mylan.connolly@protonmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Compilation failure of the kernel for drm-next Message-ID: <fbea437a-2c8b-31dc-b71b-efcfff403770@unrelenting.technology> In-Reply-To: <a30f9115-8167-5ccb-6939-cb1cd836d99e@nomadlogic.org> References: <nOeMOP-rjlkJFJsTpy7o686fAvRny3b8Kitv1ezTDdC4dAbLL8fVwDbghL6t5ap3wPVIbyqoUQJvkzDQ5e0jv3RRdj-QF2c5xnd0BqIZCs0=@protonmail.com> <a30f9115-8167-5ccb-6939-cb1cd836d99e@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/27/2018 5:03 AM, Pete Wright wrote: > > > On 02/26/2018 17:17, Mylan Connolly wrote: >> Hello all, >> >> I'm not sure if this is the best place to send this, but it looks >> like the issue tracker in Github is a bit dead. > > there may not be much traffic on it recently, but people are def still > actively working on the repository and will see when new issues are > reported. > > as of now your best to to use or test out the drm-next bits is to run > a recent 12-CURRENT with no patches applied. then you can build the > port or package via the ports tree under graphics/drm-next-kmod. it > currently runs on my end under 12-CURRENT and 11-STABLE. Yeah, and the issue tracker for drm-next-kmod is https://github.com/FreeBSDDesktop/kms-drm/issues NOT https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fbea437a-2c8b-31dc-b71b-efcfff403770>