Date: Thu, 21 Jan 2021 14:31:10 -0500 From: Robert Huff <roberthuff@rcn.com> To: Kurt Hackenberg <kh@panix.com> Cc: questions@freebsd.org Subject: Re: drm-kmod kills FreeBSD Message-ID: <24585.54910.108538.969885@jerusalem.litteratus.org> In-Reply-To: <dc52a4ab-378a-9d65-a664-43569bceae36@panix.com> References: <alpine.BSF.2.20.2101201919360.73682@tripel.monochrome.org> <CAM8r67D-TZ0ZrLO7=JWTQ5Ak2jcq%2B3P3pAXuu1HCnMrxQjG5Ow@mail.gmail.com> <alpine.BSF.2.20.2101202008490.73682@tripel.monochrome.org> <24584.64455.966459.479993@jerusalem.litteratus.org> <dc52a4ab-378a-9d65-a664-43569bceae36@panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kurt Hackenberg <kh@panix.com> : > Robert Huff wrote: > > > To do what they do, drm-kmods and gpu-firmware-kmod burrow > > _deep_ into the kernel; everything needs to be _perfectly_ in > > sync or ... <hairball!> > > They are part of the kernel, literally kernel > modules. Distributing them as ports/packages was expedient, a > quick hack. I think they should somehow be distributed as part of > the kernel. I would be OK with that _if_ there was single drm module; or, at the least, _much_ greater clarity about which module goes with a particular chipset. (On my to-do list is upgrading one system from a Radeon HD 3300 to something (AMD) that uses GCN. After weeks of research I think\\\\\hope I've found the right answer ....) Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24585.54910.108538.969885>