From owner-freebsd-x11@freebsd.org Tue Sep 5 07:28:43 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 E4447E1EE49 for ; Tue, 5 Sep 2017 07:28:43 +0000 (UTC) (envelope-from jmd@freebsd.org) Received: from www.poelloepaeae.de (v22017034403546374.happysrv.de [188.68.38.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE97081DC9 for ; Tue, 5 Sep 2017 07:28:43 +0000 (UTC) (envelope-from jmd@freebsd.org) Received: from manray.ogolem.org (HSI-KBW-134-3-230-69.hsi14.kabel-badenwuerttemberg.de [134.3.230.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by www.poelloepaeae.de (Postfix) with ESMTPSA id 6EE3518811B; Tue, 5 Sep 2017 08:49:05 +0200 (CEST) Date: Tue, 5 Sep 2017 02:48:56 -0400 From: Johannes M Dieterich To: Jan Mikkelsen Cc: freebsd-x11@freebsd.org Subject: Re: Future graphics/drm-next-kmod support on 11-STABLE? Message-ID: <20170905024856.65b47eef@manray.ogolem.org> In-Reply-To: <916E6128-4239-4050-987F-EB0816C53F13@transactionware.com> References: <916E6128-4239-4050-987F-EB0816C53F13@transactionware.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Tue, 05 Sep 2017 07:28:44 -0000 On Tue, 5 Sep 2017 10:05:16 +1000 Jan Mikkelsen wrote: > Hi, > > Thanks for the graphics work, will try it out soon. > > Does this work depend on changes in 12-CURRENT that will not be > backported to 11-STABLE? Do you expect the port to work with > 11-STABLE in future? The port does depend on rather extensive changes made to the linuxkpi in CURRENT, yes. We did discuss backporting and the current consensus seems to be that we let things stabilize in CURRENT before doing that. Hope this helps, Johannes