From owner-freebsd-current@freebsd.org Tue Sep 27 09:26:59 2016 Return-Path: Delivered-To: freebsd-current@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 923EBBEB9A5 for ; Tue, 27 Sep 2016 09:26:59 +0000 (UTC) (envelope-from me@cschwarz.com) Received: from orion.uberspace.de (orion.uberspace.de [95.143.172.79]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA4F5C8D for ; Tue, 27 Sep 2016 09:26:58 +0000 (UTC) (envelope-from me@cschwarz.com) Received: (qmail 3317 invoked from network); 27 Sep 2016 09:26:55 -0000 Received: from localhost (HELO csarch) (127.0.0.1) by orion.uberspace.de with SMTP; 27 Sep 2016 09:26:55 -0000 Date: Tue, 27 Sep 2016 11:26:52 +0200 From: Christian Schwarz To: freebsd-current@freebsd.org Subject: Re: Differences between freebsd-base-graphics and regular current source trees? Message-ID: <20160927092652.GC5074@csarch> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.2 (2016-07-01) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2016 09:26:59 -0000 On Tue, Sep 27, 2016 at 07:32:36AM +0000, Thomas Mueller wrote: > If I want to keep up with FreeBSD-current with new graphics drivers, is it sufficient to keep only the freebsd-base-graphics source tree to avoid the redundancy of keeping the regular src tree as well? I use the drm-next-4.7 branch at https://github.com/FreeBSDDesktop/freebsd-base-graphics >From what I understand, this is the repo where the current effort in syncing with Linux i915 & Radeon drivers happens. Upstream is merged from time to time, usual delay <= 2 week. I am also interested in changes to the iwm driver and maintain a branch with patches to this module that I rebase onto drm-next-4.7. Hope this helps, Christian