From owner-freebsd-current@freebsd.org Fri May 18 20:30:28 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 A71A7EDB24F; Fri, 18 May 2018 20:30:28 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 27A9868B4E; Fri, 18 May 2018 20:30:27 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Jm14fsyYTSzNNJm15fjQ1W; Fri, 18 May 2018 14:30:20 -0600 X-Authority-Analysis: v=2.3 cv=KuxjJ1eN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=8nJEP1OIZ-IA:10 a=VUJBJC2UJ8kA:10 a=xfDLHkLGAAAA:8 a=pGLkceISAAAA:8 a=7Qk2ozbKAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=ezmmrFSbtsYoodHyYowA:9 a=wPNLvfGTeEIA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id E1631CBF; Fri, 18 May 2018 13:30:17 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4IKUHHc032592; Fri, 18 May 2018 13:30:17 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4IKUHa3032589; Fri, 18 May 2018 13:30:17 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805182030.w4IKUHa3032589@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Warner Losh cc: Johannes Lundberg , FreeBSD X11 mailing list , Current FreeBSD , Steve Kargl Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Warner Losh of "Fri, 18 May 2018 14:15:03 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Fri, 18 May 2018 13:30:17 -0700 X-CMAE-Envelope: MS4wfPVw4v3slBC3yFcY1PmtlEn9vwpJQXLzoyuXPCoxUhYlEYs6Shn8bYxwJWFDubQjftfgLr4J5jzLc1FHGE2cTXOFXHXYnwW359W5BgX9iPxB/9dNv4sO iAaVuHa0Sn6x1aFgeZiRQtddH/xiH84PQVOSi0abA4FGPuNsX9AaZu/KYoDso2t5sUnKYT+i957pfwFtBJ/S7cuc+vwZwPycasDX8JGuNPKMTbu4X+Pg/0Ar qPVWzBKyP55eZqbfkPaNsdWn9IrM2DtWfFZQRBR1+U8+s4pAYOYbpjGTVcXlkepzQQsx9gUmPIqjgztCXqbybOp5/0uA+Lyny+JBCbqLLcp5JYBqbgoI6ON8 KD+jGajj/S8pNexAWsMFXnPaoyfVv8AU4PoSziUwinOqKI+jxqo= 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:30:29 -0000 In message , Warner Losh writes: > 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. Many Linux distros don't even support i386 any more. RHEL 5 was the last for Red Hat (though Fedora still does). In all fairness, we will need to bite the bullet one day too. Not suggesting anything but we should start thinking about 32-bit and planning for it (& 2038). I still have one i386 (the rest being amd64). VESA does suck on a 1280x768 monitor. The 915resolution port stopped working on it long ago. I'm not saying keep it just for this one machine, this is just a data point to the discussion. I'm also not saying to deprecate i386 now, however we should start planning for the eventuality. Maybe FreeBSD 14, 16 or beyond. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.