Date: Sun, 12 Jun 2011 11:51:11 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@FreeBSD.org> Cc: freebsd-arch@FreeBSD.org Subject: Re: [RFC] shipping kernels with default modules? Message-ID: <BDC0C06C-3152-49AF-A0F7-86A05AF14288@bsdimp.com> In-Reply-To: <BANLkTinJP%2BmSiacOO03r8zAY_79ABDy_EQ@mail.gmail.com> References: <BANLkTin2AwKRT7N6HWqBctJcT72_mR=Otg@mail.gmail.com> <BANLkTinJP%2BmSiacOO03r8zAY_79ABDy_EQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 12, 2011, at 12:36 AM, Adrian Chadd wrote: > On 11 June 2011 17:21, Adrian Chadd <adrian@freebsd.org> wrote: >=20 >> Is there any reason we aren't doing this at the moment? Eg by having = a >> default loader modules list populated from the kernel config file? >=20 > The immediate problem - how does one get the config parameters from > the kernel configuration file to appear in the per-module build setup? For options, we've been doing that for years. Config generates the = opt_foo.h files, and they are picked up by the modules. > Or, in a more general sense, how do you do per-module configuration? Generally, the modules follow the global settings, since we've never = tested building some network drivers with INET and some without, for = example. Or did you have something else in mind when you asked? Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BDC0C06C-3152-49AF-A0F7-86A05AF14288>