From owner-freebsd-current@freebsd.org Fri May 18 20:15:05 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 5DE55EDA2DF for ; Fri, 18 May 2018 20:15:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E19AE87AD5 for ; Fri, 18 May 2018 20:15:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id c5-v6so3418956itj.1 for ; Fri, 18 May 2018 13:15:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=XmM2w7NU5apdjBMXblrsT46qmZSVuBRJAN7w6CRvANQ=; b=w0GBnHnNPEMTBeTnS0FjHpv0QBWr/ygo1LBax8qr9k4p+/WdJIHpTj0CHa0eIjZBQv QIb/+VaqfmpJDXdP2K8ZO3WdU0E/2drOJa+NgEDHKeB5F4ax5nGPVaUdtcuSytdaOjwk QO+URuAguxcCQNZ1llWE5X1RWp8K20/pLGF/RBItRWZvK38MPyfcbG1nwF1lT88CjR0g NhIRUjwDzXggYNN1cSWcOnS67iQGFFo+NNdegkv/tfaBsdu4S7mK8gryIe8H/WqIOtON ci8XOOgUkbQULBnIb+42MAoqm34uXaqZYhTTynM1ChCYaV7ZCyY4PbKycHLtoDpl0zvf squQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=XmM2w7NU5apdjBMXblrsT46qmZSVuBRJAN7w6CRvANQ=; b=X91Lv1yXLXnckKdrt5V3CpJSGSxSjqcI+pDwdkprOJGIND8abqxskbhHNY0sf72nlK VrH8GiIRHoGpyLulcj6iP8/n8xrAv4oHHjHhsiYb9Lv4Z6pPXuyOQRxcKxV4IPoyUU3h pjOFgtKA70ofgMrr/8OywYEWMamyPUZOo/cbMrrsOXstyZDp10cum6Y9BZXzSjIvyNCY QZzaqHzUuji9UJaUnM5rvYj/p9Z/th0K/8+Dl2yH9WSkIFlvPvbPMNHvNAcsxtcLHyEm dXHvLTfhOzOBQ44wGJGFDIhiMIXD0clYcXQ2+36Kw3uOF7WNsJ5Q9NaueOLyvVwzMpD8 TcKg== X-Gm-Message-State: ALKqPwdaDpcs98xNy68w8yYapYvdqfN/et1anaFzzMIL7kc05hk27+Py Z8QUxNi3SW23v4DbgqWadzqByL6bOY1P9obdoxbgpQ== X-Google-Smtp-Source: AB8JxZrr4Q2/ZvbONs/3smyzDHqE+N9mEwut0xRonLEw4hE7TeyDE+wNPbTDgBJSP8bS9TPObLFz2yhnHJM44Le7a0g= X-Received: by 2002:a24:6ec1:: with SMTP id w184-v6mr8255645itc.57.1526674504030; Fri, 18 May 2018 13:15:04 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Fri, 18 May 2018 13:15:03 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Warner Losh Date: Fri, 18 May 2018 14:15:03 -0600 X-Google-Sender-Auth: N-jzcsq-0OflMXWhV4tIabisjak Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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:15:05 -0000 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, a= nd >> > > > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konst= antin 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 a= nd >> > > > 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 dr= m2 >> > > > driver on 12-CURRENT? If so, what is preventing you from switchin= g >> 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=3D amd64 >> > ONLY_FOR_ARCHS_REASON=3D 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