From owner-freebsd-current@FreeBSD.ORG Mon Feb 27 14:32:22 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 B117616A420; Mon, 27 Feb 2006 14:32:22 +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 3C9EC43D49; Mon, 27 Feb 2006 14:32:21 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k1REVheO041208; Mon, 27 Feb 2006 07:31:43 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44030D4E.5010600@samsco.org> Date: Mon, 27 Feb 2006 07:31:42 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yar Tikhiy References: <20060225140509.GC79616@comp.chem.msu.su> <44008314.8030205@samsco.org> <20060225201102.GA6936@pint.candc.home> <20060227121305.GO6435@comp.chem.msu.su> In-Reply-To: <20060227121305.GO6435@comp.chem.msu.su> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org, cokane@freebsd.org, Coleman Kane 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 14:32:22 -0000 Yar Tikhiy wrote: > On Sat, Feb 25, 2006 at 03:11:02PM -0500, Coleman Kane wrote: > >>I have unfortunately lost all of my voodoo hardware. >> >>On Sat, Feb 25, 2006 at 09:17:24AM -0700, Scott Long wrote: >> >>>Yar Tikhiy wrote: >>> >>>>Hi there, >>>> >>>>In the course of reviewing and cleaning up the default configuration >>>>of kernel options, it was suggested by the Release Engineers that >>>>we had a separate module for TDFX_LINUX instead of placing the >>>>burden on the device tdfx and module 3dfx. Could anybody interested >>>>test this change? I've made sure it builds, but I have no 3dfx hw >>>>to really test it. The testing is as simple as building the new >>>>3dfx and 3dfx_linux modules, loading them, and verifying that the >>>>linux apps work with the device as before. Thanks in advance! >>>> >> >>Sounds goo to me. I am all for further modularization of the codebase. > > > Thanks! > > >>>Why keep the TDFX_LINUX option defined in sys/conf/options? >> >>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. > It's a little confusing though since it's now treated as a separate driver. Scott