Date: Mon, 27 Feb 2006 13:16:10 -0500 From: Coleman Kane <cokane@cokane.org> To: Scott Long <scottl@samsco.org> Cc: Yar Tikhiy <yar@comp.chem.msu.su>, current@freebsd.org, cokane@freebsd.org Subject: Re: RFC: separate 3dfx_linux module Message-ID: <20060227181610.GB6099@pint.candc.home> In-Reply-To: <44033D92.2020009@samsco.org> References: <20060225140509.GC79616@comp.chem.msu.su> <44008314.8030205@samsco.org> <20060225201102.GA6936@pint.candc.home> <20060227121305.GO6435@comp.chem.msu.su> <20060227175740.GA6099@pint.candc.home> <44033D92.2020009@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 27, 2006 at 10:57:38AM -0700, Scott Long wrote: > Coleman Kane wrote: > >On Mon, Feb 27, 2006 at 03:13:05PM +0300, Yar Tikhiy wrote: > > > >> > >>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 > > Ok, I envisioned this as: > > device tdfx > device tdfxlinux # Optional Linux compatibility > > I don't have a strong opinion on it, and I'll defer to whatever Coleman > and Yar think is most appropriate. My impression was more that the current config format would stay the same, but there'd be separate modules (rather than incorporating it all into tdfx.ko): tdfx.ko tdfx_linux.ko Much like how wlan.ko and wlan_*.ko operate? > > SCott >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060227181610.GB6099>