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_at_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_at_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? -- SteveReceived on Mon May 21 2018 - 18:32:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC