From owner-freebsd-current@FreeBSD.ORG Mon Feb 27 17:53:54 2006 Return-Path: X-Original-To: current@freebsd.org 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 DAFF316A42B for ; Mon, 27 Feb 2006 17:53:54 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from smtp3.fuse.net (mail-out3.fuse.net [216.68.8.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6B2E43D49 for ; Mon, 27 Feb 2006 17:53:49 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from gx6.fuse.net ([216.196.181.22]) by smtp3.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060227175348.DLCV25315.smtp3.fuse.net@gx6.fuse.net> for ; Mon, 27 Feb 2006 12:53:48 -0500 Received: from mail.cokane.org ([216.196.181.22]) by gx6.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060227175348.JXTU4722.gx6.fuse.net@mail.cokane.org> for ; Mon, 27 Feb 2006 12:53:48 -0500 Received: (qmail 6104 invoked by uid 1000); 27 Feb 2006 12:57:40 -0500 Date: Mon, 27 Feb 2006 12:57:40 -0500 From: Coleman Kane To: Yar Tikhiy Message-ID: <20060227175740.GA6099@pint.candc.home> References: <20060225140509.GC79616@comp.chem.msu.su> <44008314.8030205@samsco.org> <20060225201102.GA6936@pint.candc.home> <20060227121305.GO6435@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060227121305.GO6435@comp.chem.msu.su> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Mon, 27 Feb 2006 18:19:07 +0000 Cc: current@freebsd.org, cokane@freebsd.org Subject: Re: RFC: separate 3dfx_linux module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 27 Feb 2006 17:53:55 -0000 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