From owner-freebsd-current@FreeBSD.ORG Sat Feb 25 20:08:57 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 6B2A116A420 for ; Sat, 25 Feb 2006 20:08:57 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA7D143D55 for ; Sat, 25 Feb 2006 20:08:56 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from gx6.fuse.net ([216.196.181.22]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060225200855.HKXS12076.smtp2.fuse.net@gx6.fuse.net> for ; Sat, 25 Feb 2006 15:08:55 -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 <20060225200855.CGML4722.gx6.fuse.net@mail.cokane.org> for ; Sat, 25 Feb 2006 15:08:55 -0500 Received: (qmail 6941 invoked by uid 1000); 25 Feb 2006 15:11:02 -0500 Date: Sat, 25 Feb 2006 15:11:02 -0500 From: Coleman Kane To: Scott Long Message-ID: <20060225201102.GA6936@pint.candc.home> References: <20060225140509.GC79616@comp.chem.msu.su> <44008314.8030205@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44008314.8030205@samsco.org> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Sat, 25 Feb 2006 21:03:51 +0000 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: Sat, 25 Feb 2006 20:08:57 -0000 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. > > 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 ? > > Scott >