From owner-freebsd-current@freebsd.org Fri Aug 24 16:16:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 112CD108E2F2 for ; Fri, 24 Aug 2018 16:16:40 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93DF78CAAB for ; Fri, 24 Aug 2018 16:16:39 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 10998061-a7b9-11e8-aff6-0b9b8210da61 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 10998061-a7b9-11e8-aff6-0b9b8210da61; Fri, 24 Aug 2018 16:16:34 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w7OGGVXK000911; Fri, 24 Aug 2018 10:16:31 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1535127391.1488.23.camel@freebsd.org> Subject: Re: priority of paths to kernel modules? From: Ian Lepore To: Cy Schubert , Johannes Lundberg , freebsd-current Date: Fri, 24 Aug 2018 10:16:31 -0600 In-Reply-To: <20180824153611.7F83C1AC@spqr.komquats.com> References: <20180824153611.7F83C1AC@spqr.komquats.com> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2018 16:16:40 -0000 On Fri, 2018-08-24 at 08:35 -0700, Cy Schubert wrote: > 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. > This seems like the obvious fix. I thought the whole point of all this is that we support drm2 on some platforms, but not x86 anymore. So to me that implies not building the modules by default on x86. -- Ian > --- > Sent using a tiny phone keyboard. > Apologies for any typos and autocorrect. > Also, this old phone only supports top post. Apologies. > > Cy Schubert > or > 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/ > 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/ 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd > .org" > > _______________________________________________ > 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"