From owner-freebsd-current@freebsd.org  Tue Feb 27 08:51:48 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 893C4F313E3
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 27 Feb 2018 08:51:48 +0000 (UTC)
 (envelope-from greg@unrelenting.technology)
Received: from hraggstad.unrelenting.technology
 (hraggstad.unrelenting.technology [71.19.146.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "hraggstad.unrelenting.technology",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 020AF6A18E
 for <freebsd-current@freebsd.org>; Tue, 27 Feb 2018 08:51:47 +0000 (UTC)
 (envelope-from greg@unrelenting.technology)
Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id
 b89df967
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO;
 Tue, 27 Feb 2018 08:51:33 +0000 (UTC)
Subject: Re: Compilation failure of the kernel for drm-next
To: Pete Wright <pete@nomadlogic.org>,
 Mylan Connolly <mylan.connolly@protonmail.com>,
 "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
References: <nOeMOP-rjlkJFJsTpy7o686fAvRny3b8Kitv1ezTDdC4dAbLL8fVwDbghL6t5ap3wPVIbyqoUQJvkzDQ5e0jv3RRdj-QF2c5xnd0BqIZCs0=@protonmail.com>
 <a30f9115-8167-5ccb-6939-cb1cd836d99e@nomadlogic.org>
From: Greg V <greg@unrelenting.technology>
Message-ID: <fbea437a-2c8b-31dc-b71b-efcfff403770@unrelenting.technology>
Date: Tue, 27 Feb 2018 11:51:30 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <a30f9115-8167-5ccb-6939-cb1cd836d99e@nomadlogic.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Feb 2018 08:51:48 -0000

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