Date: Thu, 24 May 2001 12:32:12 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: "Long, Scott" <scott_long@btc.adaptec.com> Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Bruce Evans <bde@FreeBSD.org>, Peter Wemm <peter@wemm.org>, Bruce Evans <bde@zeta.org.au>, Cameron Grant <gandalf@vilnya.demon.co.uk> Subject: RE: cvs commit: src/sys/gnu/dev/sound/pci emu10k1.h maestro3_dsp Message-ID: <XFMail.010524123212.jhb@FreeBSD.org> In-Reply-To: <DE0BBA556B46D511BB5F0000D11ABE9228CC1C@btcexc01.btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24-May-01 Long, Scott wrote: > To add further clarity to this mud-pit: > > 1. pcm *IS* in GENERIC in -current. It was added by Jordan last > fall, IIRC. > 2. pcm *IS NOT* in GENERIC in -stable, nor any official release. > 3. I did not put maestro3 into sys/conf/files for two reasons: > a. I wanted the user to be aware that he/she is using a driver that > has components which do not fall under the 'default' BSD > license, and instead falls under the GPL (namely, the firmware). > b. -current snapshots are occasionally built and available to the > public, meaning that pcm-enabled GENERIC kernels are built. I > did not want to risk muddying the kernel in this way. It should still be in LINT. We need LINT to build everything when we are testing kernel changes. Please fix. You might want to use a separate kernel option to enable support for GPL'd pcm drivers, which LINT would specify but GENERIC would not. > I agree with Cameron that there is no reason that pcm and it's children > should not be loaded as modules, If you are debugging kernels there is. :) It's far too easy to get a kernel and modules out of sync in this fashion, and having a monolithic kernel with no modules is the safest way of preventing foot shooting in this case. I use no modules unless I absolutely have to due to brokennes. (For example, screen savers cant be compiled statically, which is just due to them not being put in sys/conf/* and options added for them.) > but there are many out there that resist > the use of modules and still like their kernel to be monolithically built. > For this reason I wish that 'device pcm' was not an unmitigated shotgun > that puts every sound driver in. If config could be modified to allow > the exclusion of drivers like maestro3 and emu10k1 on a configurable > basis, I think that this confusion could be solved. Thoughts? Agreed. It's not a bad thing to resist modules. Modules are only really useful in certain situations. > Scott -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010524123212.jhb>