On Thu, Nov 02, 2023 at 04:12:43PM +0000, Robert Swindells wrote:
>
> tlaro...@kergis.com wrote:
> > As stated in a message before, disabling, via userconf(4), all the
> > drmkms drivers can not rely on a pattern matching since, for historical
> > reasons (several versions of DRM), the namespace of the drivers is not
> > "ruled".
>
> I don't see the need for this, it would be unusual for more than one
> drm driver to attach.
>
> You can also build a custom kernel.
The problem is when installing a GENERIC kernel.
You don't know, a priori, what will be encountered.
Been there: I installed a "generic" distribution on a lended baremetal
remote server (without any access except ssh when it comes up), and
NetBSD failed to work, because of the drmkms/
And there can be more than one drmkms driver. It is not unusual to
have a GPU integrated (on board) and a discrete one (on an extension).
The goal is to provide a way to disable drmkms entirely without
knowing what the kernel will actually encounter.
--
Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
