From owner-freebsd-x11@freebsd.org Thu May 25 19:17:05 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69515D82ECC for ; Thu, 25 May 2017 19:17:05 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A9D981847 for ; Thu, 25 May 2017 19:17:03 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id v4PIuTPw029088 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 May 2017 13:56:29 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id v4PIuTSs029087; Thu, 25 May 2017 13:56:29 -0500 (CDT) (envelope-from bob) Date: Thu, 25 May 2017 13:56:29 -0500 From: Bob Willcox To: Pete Wright Cc: freebsd-x11@freebsd.org Subject: Re: status of drm-next[-4.7]? Message-ID: <20170525185629.GC28184@rancor.immure.com> Reply-To: Bob Willcox References: <20170525184301.GA80569@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2017 19:17:05 -0000 On Thu, May 25, 2017 at 11:44:36AM -0700, Pete Wright wrote: > > > On 05/25/2017 11:43, Steve Kargl wrote: > > I have a Dell Precision 7510 mobile workstation on which > > I installed the drm-next-4.7 branch (using instructions > > from [1]) to get her up and running. That installation > > was done of Nov 16, 2016. > > > > I would like to upgrade to top-of-tree FreeBSD, but it > > seems that trunk has not been merged into the drm-next-4.7 > > branch for several months. Have sufficient patches been > > merged from the drm-next-4.7 branch into trunk to allow > > me to starting tracking stock FreeBSD-current? > > Current development has been happening in the "drm-next" branch on > github. This gets sync'd with upstream CURRENT on a weekly basis more > or less, and is under active development and regression testing. > > Hope that helps! > -pete That's good to hear. I'm running an Intel NUC with an i7-5557U with a Broadwell CPU that I installed the drm-next on about two months ago. Is there any estimate of when the drm-next changes might get merged into the CURRENT branch? -- Bob Willcox | Lawsuit, n.: A machine which you go into as a pig and bob@immure.com | come out as a sausage. Austin, TX | -- Ambrose Bierce