Date: Sun, 26 Aug 2018 21:22:28 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Subject: Re: priority of paths to kernel modules? Message-ID: <20180826212228.f7dff763c78ead18a356a206@dec.sakura.ne.jp> In-Reply-To: <CANCZdfpgDSDyv6ZjrKT0BdrXempng9knbeBoMvytJkvynxx0Dg@mail.gmail.com> References: <CACNAnaGMsifVntGHQ8T4-w6jL%2B2dx5e1Ciw3-CQ9W2MwF38mfg@mail.gmail.com> <201808241411.w7OEBXg8095140@pdx.rh.CN85.dnsmgr.net> <CANCZdfoNdFHM6Z8KVNrUCFzASjRLsd=dkw_fZGpJjsYmFzySUg@mail.gmail.com> <a67c3e82-838f-dd09-64d3-abb7dbcdd8e7@freebsd.org> <CANCZdfpgDSDyv6ZjrKT0BdrXempng9knbeBoMvytJkvynxx0Dg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
+1. If modules needed are recognized correctly and specified with full-path like /boot/modules/drm.ko, the priority wouldn't matter. On Fri, 24 Aug 2018 17:29:19 -0600 Warner Losh <imp@bsdimp.com> wrote: > On Fri, Aug 24, 2018 at 4:20 PM Niclas Zeising <zeising@freebsd.org> wrote: > > > On 08/24/18 17:20, Warner Losh wrote: > > > This would allow the graphics port to have a rc script that sets > > > this up so when X11 goes to automatically load the module, the right one > > > gets loaded. > > > > > > > I just want to point out that X11 doesn't load the graphics kernel > > driver by default when using the drm-*-kmod ports, and I'm not sure the > > hack to have the intel ddx (xf86-video-intel) load the drm2 driver is > > still around. > > > > It doesn't really matter though, since upstream is moving away from > > having X load the driver, and I'd like us to follow suit by using > > devmatch (this is one of the reasons we wanted to get rid of the base > > drivers, as I've stated before). X can't always know which driver to > > load (when using modesetting for instance), and in my opinion, it should > > be the kernel/loader that decides which drivers to load. > > > Excellent. That reduces the compatibility matrix I need to consider. I have > some ideas, and will hack on them to see if a clever bit of slide of hand > will solve the main problem of loading the wrong driver in a dependency > chain. > > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180826212228.f7dff763c78ead18a356a206>