Date: Mon, 21 May 2018 13:32:10 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: "K. Macy" <kmacy@freebsd.org> Cc: Rozhuk Ivan <rozhuk.im@gmail.com>, 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: <20180521203210.GA17892@troutmask.apl.washington.edu> In-Reply-To: <CAHM0Q_OQNv3VcAJyM=t3NR8HdAR7-M-Y8rDLFwNWxCr%2BwVLNnA@mail.gmail.com> 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> <CAHM0Q_OQNv3VcAJyM=t3NR8HdAR7-M-Y8rDLFwNWxCr%2BwVLNnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 21, 2018 at 01:16:12PM -0700, K. Macy wrote: > On Mon, May 21, 2018 at 10:07 AM, Steve Kargl > <sgk@troutmask.apl.washington.edu> wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter <oliver.pinter@hardenedbsd.org> wrote: >>> >>>>> One of the reasons for the deprecation and removal of the drm2 bits >>>>> is that they prevent us from automatically loading the >>>>> drm-next/stable-kmod kernel modules, since the two collide. >>>>> Regards >>>> >>>> Then it wold be better to resolve this problem, rather then removing a >>>> working solution. What's about module versioning what in other cases >>>> works? >>> >>> May be just move old drm2 to ports? >> >> 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. >> > <strawman ... clipped> Wasn't a strawman. Is it that difficult to use the Makefile infrastructure to exclude old drm2 on amd64? -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180521203210.GA17892>