From owner-freebsd-current@freebsd.org Fri May 18 20:23:13 2018 Return-Path: Delivered-To: freebsd-current@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 A1378EDAA68; Fri, 18 May 2018 20:23:13 +0000 (UTC) (envelope-from benjamin.widawsky@intel.com) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga105.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17FEA6837D; Fri, 18 May 2018 20:23:12 +0000 (UTC) (envelope-from benjamin.widawsky@intel.com) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 13:22:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208";a="47792449" Received: from gmoli3-mobl.amr.corp.intel.com (HELO localhost) ([10.252.128.225]) by fmsmga002.fm.intel.com with ESMTP; 18 May 2018 13:22:01 -0700 Date: Fri, 18 May 2018 13:22:01 -0700 From: Ben Widawsky To: Warner Losh Cc: Johannes Lundberg , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Fri, 18 May 2018 20:23:13 -0000 On 18-05-18 14:15:03, Warner Losh wrote: > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > wrote: > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >> sgk@troutmask.apl.washington.edu> wrote: > >> > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > >> wrote: > >> > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > >> > > > removed from 12.0, as was done for other drivers recently. Some > >> > > > background and rationale: > >> > > > > >> > > > The drm2 driver was the original port of a KMS driver to FreeBSD. > >> It > >> > > > was done by Konstantin Belousov to support Intel graphics cards, and > >> > > > later extended by Jean-Sébastien Pédron as well as Konstantin to > >> match > >> > > > what's in Linux 3.8. This included unstable support from Haswell, > >> but > >> > > > nothing newer than that. > >> > > > > >> > > > For quite some time now we have had the graphics/drm-stable-kmod and > >> > > > graphics/drm-next-kmods which provides support for modern AMD and > >> Intel > >> > > > graphics cards. These ports, together with the linuxkpi, or lkpi, > >> has > >> > > > made it significantly easier to port and update our graphics > >> drivers. > >> > > > Further, these new drivers cover the same drivers as the old drm2 > >> > driver. > >> > > > > >> > > > What does the community think? Is there anyone still using the drm2 > >> > > > driver on 12-CURRENT? If so, what is preventing you from switching > >> to > >> > > > the port? > >> > > > > >> > > > Thank you > >> > > > Regards > >> > > > -- > >> > > > Niclas Zeising > >> > > > FreeBSD x11/graphics team > >> > > > _______________________________________________ > >> > > > freebsd-current@freebsd.org mailing list > >> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > >> > freebsd.org" > >> > > > > >> > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion and > >> > > problems and it solves nothing. > >> > > > >> > > >> > Check the Makefiles > >> > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > >> > > >> > ONLY_FOR_ARCHS= amd64 > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on > >> amd64 > >> > > >> > Not to ia32 friendly. > >> > > >> > >> So do people use i386 for desktop? And need the latest KMS stuff? > >> > > > > Yeah I was wondering the same.. If you're running i386, do you need drm > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > remember correctly, scfb is UEFI only) > > I do feel sorry for anyone who would have to revert back to VESA... > > > > Would it be too much trouble to move it to a port? > > > > If there's someone who needs it for i386, and wants to do the work and > maintain it, we should allow it. But the drm2 maintainers have said its > likely totally broken anyway. > > Warner As a long time developer in drm/i915, and newly interested in FreeBSD (ie. no history on the matter), is there some upside and/or desire to have native support, or is the drm-next-kmod solution good enough?