Date: Tue, 22 May 2018 01:15:43 +0300 From: Rozhuk Ivan <rozhuk.im@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Oliver Pinter <oliver.pinter@hardenedbsd.org>, Niclas Zeising <zeising+freebsd@daemonic.se>, Warner Losh <imp@bsdimp.com>, FreeBSD X11 mailing list <freebsd-x11@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522011543.3f621882@gmail.com> In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <CAPS9%2BSv6SDWkbrEZruM4g2%2BOfw4ksvbtiMF=Q_towrMtJrgt1w@mail.gmail.com> <20180518193009.GA88432@troutmask.apl.washington.edu> <CANCZdfoMrFCyPteChSWgfYRY-uOyazzR0ZbYvp_OVmXRTe-Hqw@mail.gmail.com> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <CAPQ4ffvd1da%2BiMXtPfz%2BxETqPZwgmNoBa5yZMSF26qPMkSD2qQ@mail.gmail.com> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 May 2018 10:07:28 -0700 Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to exclude > drm2 from build of amd64. > > I don't use netgraph or any of the if_*.ko modules. > Can we put all of that into ports? I don't use any > scsi controllers, so those can go too. Why make it > insanely fun for users to configure a FreeBSD system. > I just ask. Or why not include drm-next to base svn repo and add some option to make.conf to swith drm2/dem-next ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180522011543.3f621882>