From owner-freebsd-current@FreeBSD.ORG Thu Aug 14 21:47:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE86537B401; Thu, 14 Aug 2003 21:47:01 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8219A43FBF; Thu, 14 Aug 2003 21:47:00 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h7F4kIFO024677; Thu, 14 Aug 2003 22:46:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 14 Aug 2003 22:40:14 -0600 (MDT) Message-Id: <20030814.224014.08945805.imp@bsdimp.com> To: jhb@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <16187.44785.91962.402945@grasshopper.cs.duke.edu> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: lchen@briontech.com cc: gallatin@cs.duke.edu cc: current@freebsd.org Subject: Re: Change to kernel+modules build approach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Aug 2003 04:47:02 -0000 In message: John Baldwin writes: : : On 14-Aug-2003 Andrew Gallatin wrote: : > : > John Baldwin writes: : > > : > > On 14-Aug-2003 Ruslan Ermilov wrote: : > > > On Thu, Aug 14, 2003 at 02:10:19AM -0600, Scott Long wrote: : > > >> Luoqi Chen wrote: : > > > [...] : > > >> >On the other hand, all modules should create all the opt_*.h files : > > >> >it needs when built individually. Add opt_ddb.h to nullfs's Makefile : > > >> >should fix the breakage. : > > >> > : > > >> Our kernel build system isn't set up to handle passing config options : > > >> to modules. Various solutions to this have been proposed, but nothing : > > >> has appeared yet. In 5.x, we document that modules will not work with : > > >> PAE. : > > >> : > > > How does the below look? This is basically a more generic implementation : > > > of Luoqi's idea, but for -CURRENT: : > > : > > I would prefer something far more radical that would involve moving : > > all the module metadata to sys/conf (i.e. removing sys/modules) and : > > building all the modules based on a single kernel config file. : > : > Would this tie modules to that kernel config? If so, would it mean : > the end of the ability of 3rd party developers to ship binary drivers : > and expect them to work with any kernel? : : Well, yes, but, one could always build generic modules by using : a kernel config containing 'options KLD_MODULE' or some such. : This would allow one to compile optimized modules if they wanted to, : but still provide the ability to build fully generic modules. This sounds like an either or choice. I don't care too much if the third party drivers aren't hyper optimzied for my kernel. But to force users of them to use some generic kernel would be a big support nightmare. Warner