Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Feb 2018 18:03:54 -0800
From:      Pete Wright <pete@nomadlogic.org>
To:        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:  <a30f9115-8167-5ccb-6939-cb1cd836d99e@nomadlogic.org>
In-Reply-To: <nOeMOP-rjlkJFJsTpy7o686fAvRny3b8Kitv1ezTDdC4dAbLL8fVwDbghL6t5ap3wPVIbyqoUQJvkzDQ5e0jv3RRdj-QF2c5xnd0BqIZCs0=@protonmail.com>
References:  <nOeMOP-rjlkJFJsTpy7o686fAvRny3b8Kitv1ezTDdC4dAbLL8fVwDbghL6t5ap3wPVIbyqoUQJvkzDQ5e0jv3RRdj-QF2c5xnd0BqIZCs0=@protonmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help


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.

cheers,
-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a30f9115-8167-5ccb-6939-cb1cd836d99e>