From owner-freebsd-x11@freebsd.org Thu Feb 28 19:15:16 2019 Return-Path: Delivered-To: freebsd-x11@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 8965015140BF for ; Thu, 28 Feb 2019 19:15:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 21AD182F32 for ; Thu, 28 Feb 2019 19:15:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id x1SJFBHb018350 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 28 Feb 2019 11:15:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x1SJFBtO018349; Thu, 28 Feb 2019 11:15:11 -0800 (PST) (envelope-from sgk) Date: Thu, 28 Feb 2019 11:15:11 -0800 From: Steve Kargl To: Cy Schubert Cc: freebsd-arch@freebsd.org, Yoshihiro Ota , Warner Losh , "freebsd-arch@freebsd.org" , FreeBSD X11 mailing list , greg@unrelenting.technology Subject: Re: DRM removal soon Message-ID: <20190228191511.GA18089@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20190223003126.4aec5a01b77ec9bf9ea0992a@j.email.ne.jp> <1550926557.1795.0@unrelenting.technology> <20190223234351.0addf9de71953eb31136322b@j.email.ne.jp> <20190228004220.fb3ed982fa8a34252ec19bb5@j.email.ne.jp> <603D07F7-CA80-40C6-8D55-3DC6EABE667E@cschubert.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <603D07F7-CA80-40C6-8D55-3DC6EABE667E@cschubert.com> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 21AD182F32 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 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, 28 Feb 2019 19:15:16 -0000 On Thu, Feb 28, 2019 at 10:49:51AM -0800, Cy Schubert wrote: > On February 27, 2019 9:42:20 PM PST, Yoshihiro Ota wrote: > >On Sun, 24 Feb 2019 10:24:15 -0700 > >Warner Losh wrote: > > > >> On Sun, Feb 24, 2019, 3:31 AM Yoshihiro Ota > >wrote: > >> > >> I also found that running kldstat was the easiest way to find which > >of > >> > driver to use instead of dmesg. > >> > > >> > >> Is this a suggestion for changing the drm-kmod package output? Or > >just a > >> helpful hint for others? > >> > >> Tanks again. > >> > >> Warner > > > >This is a helpful hint for others and a suggestion to update documents. > > > >I had read > >https://www.freebsd.org/releases/12.0R/relnotes.html#hardware-graphics > >and https://wiki.freebsd.org/Graphics before I started. I had 4 old > >laptops and 1 vmawre and I didn't remember which machine uses which CPU > >:) > >If the doc can mention to check kldstat output and go to corresponding > >section, that will make steps easier. > > > >I converted to the port based driver for 4 psychical machines and 1 > >vmware machine (although vmware do not use neither of driver.) All of > >them run 12.0-RELEASE. All of them start X and work fine. I will > >likely get to 13-CURRENT a lot later as I ran 13-CURRENT without X and > >in vmware most of times. > > > > > The ports work as advertised. IMO graphics/drm-legacy should be > depreciated sooner than later. I would expect the graphics team > could better spend their time and energy on drm-current, which > btw works perfectly on my old laptop converted to i386 testbed, > than maintaining old bitrot. When can we expect drm-legacy to > finally be removed from ports? > drm-legacy-kmd has already been *depreciated*? Perhaps, you meant deprecated. :) Hopefully, never. drm-current-kmod locks up my laptop. drm-legacy-kmod works. -- Steve