From owner-freebsd-x11@freebsd.org Sun Sep 3 17:38:29 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 0224CE16389; Sun, 3 Sep 2017 17:38:29 +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 BECD672D8F; Sun, 3 Sep 2017 17:38:28 +0000 (UTC) (envelope-from jmd@freebsd.org) Received: from manray.ogolem.org (c-73-195-214-55.hsd1.nj.comcast.net [73.195.214.55]) (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 2172A18811B; Sun, 3 Sep 2017 19:00:21 +0200 (CEST) Date: Sun, 3 Sep 2017 13:00:17 -0400 From: Johannes M Dieterich To: Cy Schubert Cc: blubee blubeeme , David Chisnall , freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] future of drm1 in base Message-ID: <20170903130017.0a5fdc36@manray.ogolem.org> In-Reply-To: <201709031651.v83Gp3He026291@slippy.cwsent.com> References: <201709031651.v83Gp3He026291@slippy.cwsent.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: Sun, 03 Sep 2017 17:38:29 -0000 On Sun, 03 Sep 2017 09:51:03 -0700 Cy Schubert wrote: > (Replying inline) > In message > om> > , blubee blubeeme writes: > > I also have a current machine with one of those listed gpu. > > > > A friend got hacked on windows, I got them setup with a ryzen chip > > and no integrated GPU. Finding a supported gpu was a challenge but, > > those old drivers allow the machine to have display. > > > > Please try to maintain the older drivers, thanks. Well, from now on you can recommend also AMD Tahiti up to Polaris alongside the binary Nvidia driver, assuming the system is amd64. :-) > > I wouldn't mind taking care of and feeding the new port if it's > created. Thank you! It does look to me that there is a need for continued support to exist. So we will create a port now and then I will propose removal of drm1 from base so that users of graphics/drm-next-kmod and graphics/drm-legacy-kmod can more easily co-exist in the future. I will probably issue a CFT after the port landed to make sure that everything still works and would much appreciate if people with the hardware could give it a spin. Thank you everybody for your responses! Johannes