Date: Fri, 15 Feb 2019 09:41:16 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: sgk@troutmask.apl.washington.edu, Steve Kargl <sgk@troutmask.apl.washington.edu>, Johannes Lundberg <johalun0@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: "DRM removal soon" is premature Message-ID: <6531965D-0E8D-479F-8773-F166651C9334@cschubert.com> In-Reply-To: <20190215155026.GA9317@troutmask.apl.washington.edu> References: <20190214180101.GB67712@troutmask.apl.washington.edu> <CANCZdfqy%2Bs3QtEu%2BAhTm-HoJfByjeA9EeUGZ_3VrThvrcWvBow@mail.gmail.com> <20190214182419.GA67872@troutmask.apl.washington.edu> <CANCZdfrBTjV-rqU-VNRkFeQV2449ebgqi9qAAXYR6J_wygfxPg@mail.gmail.com> <20190214190244.GA68143@troutmask.apl.washington.edu> <CANCZdfqx%2BnLoV_bJU0cARxgz4ZBR-X_eZyFCVWzozuir5FqwnQ@mail.gmail.com> <20190214191739.GA68371@troutmask.apl.washington.edu> <20190214225810.kmfxzeuvr7t7gget@smtp.freebsd.org> <20190214233000.GA2752@troutmask.apl.washington.edu> <3b0ba403-ff96-8c94-6d98-40165473d1f3@gmail.com> <20190215155026.GA9317@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On February 15, 2019 7:50:26 AM PST, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: >On Fri, Feb 15, 2019 at 09:07:08AM +0000, Johannes Lundberg wrote: >> >> This happens all time for me with virtualbox-kmod as well in current. >> Changes to src breaks certain (kmod) ports and there's always a delay >> until they are fixed. This is life in -CURRENT. I accept this and >don't >> go bitching to virtualbox-kmod maintainers about it. Your usage is an >> edge case so naturally there will be a longer delay before breakage >is >> noticed, until we can get automated CI up and running (even so, there >> will be a delay). >> > >Was virtualbox-kmod every a part of the FreeBSD base sytem? > >drm2 was a part of the base system and it was functional >until it was unhooked from the build. The issue with the >merged PAE vs. non-PAE i386/pmap.h would have been identified >prior to it being committed if either drm2 had not been >unhooked or if an exp-run over ports was run. > >I also don't see how this is an edge case. A part of drm2 >removal was the creation of a port, so those who don't have >the luxury of updating hardware every year can continue to >use drm2. If this type of breakage of functionality formerly >in base, and the name calling of someone pointing out the >breakage, is the new norm, then it is a harbinger of doom for >pkg-base. Just to add a data point, I use drm-current on a 13 year old i386 laptop running -current, used as an i386 test platform. Keeping it in sync with my amd64 platforms. -- Pardon the typos and autocorrect, small keyboard in use. Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6531965D-0E8D-479F-8773-F166651C9334>