Date: Mon, 27 Feb 2006 12:57:40 -0500 From: Coleman Kane <cokane@cokane.org> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: current@freebsd.org, cokane@freebsd.org Subject: Re: RFC: separate 3dfx_linux module Message-ID: <20060227175740.GA6099@pint.candc.home> In-Reply-To: <20060227121305.GO6435@comp.chem.msu.su> References: <20060225140509.GC79616@comp.chem.msu.su> <44008314.8030205@samsco.org> <20060225201102.GA6936@pint.candc.home> <20060227121305.GO6435@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 27, 2006 at 03:13:05PM +0300, Yar Tikhiy wrote: > On Sat, Feb 25, 2006 at 03:11:02PM -0500, Coleman Kane wrote: > > > > Sounds good to me. In the event that you want to build this statically > > into the kernel, doesn't the option still need to be available, > > or are we talking about a device tdfxlinux ? > > It was exactly my point, too: the TDFX_LINUX option has to be there > so that people still can compile device tdfx with Linux support into > the main kernel file. Not to mention so that they can omit said functionality if it is not desired. I believe that the kmod by default compiles this in though. > > -- > Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060227175740.GA6099>