RE: priority of paths to kernel modules?

My idea, which I implemented locally and should probably create a phab review, was to ifdef DRM in modules/Makefile. We could do this too. Default not to build/install.

---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.

Cy Schubert
<Cy.Schubert_at_cschubert.com> or <cy_at_freebsd.org>
The need of the many outweighs the greed of the few.
---

-----Original Message-----
From: Johannes Lundberg
Sent: 24/08/2018 01:08
To: freebsd-current
Subject: priority of paths to kernel modules?

Hi

Since we now stuck with drm2 in base for a few more years I have an idea
would make things much smoother for many of us, hugely reduce the amount of
bug reports we get and I think would be beneficial in other ways too.

Current I run with something like this in /boot/loader.conf

module_path="/boot/modules.drm-v4.16;/boot/modules;/boot/dtb;/boot/overlays"

So I expect modules to be loaded in that order, with /boot/<mykernel> LAST.

However, if you look at this
sysctl kern.module_path
kern.module_path:
/boot/kernel;/boot/modules.drm-v4.16;/boot/modules;/boot/dtb;/boot/overlays

/boot/kernel is inserted first and probably modules in /boot/kernel have
the highest priority. This is also proven by everyone wanting to use
drm*kmods that get drm.ko from base loaded instead of the installed in
/boot/modules.

Please correct me if I'm wrong but if my understanding is correct this is a
flaw and /boot/<mykernel> should be inserted last so that any overlays or
custom modules have higher priority than the default ones.

I can imagine this is also useful when building custom modules and you
don't want to overwrite or delete the default one in /boot/kernel...

Cheers
_______________________________________________
freebsd-current_at_freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"