From owner-freebsd-current@FreeBSD.ORG Mon Feb 27 17:58:11 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 AA79A16A420; Mon, 27 Feb 2006 17:58:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EBB543D4C; Mon, 27 Feb 2006 17:58:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k1RHviHG042371; Mon, 27 Feb 2006 10:57:44 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44033D92.2020009@samsco.org> Date: Mon, 27 Feb 2006 10:57:38 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Coleman Kane 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> In-Reply-To: <20060227175740.GA6099@pint.candc.home> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Yar Tikhiy , 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:58:12 -0000 Coleman Kane wrote: > 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 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. SCott