From owner-freebsd-current@FreeBSD.ORG Tue Feb 28 00:52:26 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 2402616A420 for ; Tue, 28 Feb 2006 00:52:26 +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 2B3E743D48 for ; Tue, 28 Feb 2006 00:52:25 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from gx4.fuse.net ([216.196.181.22]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060228005224.FHGU12076.smtp2.fuse.net@gx4.fuse.net> for ; Mon, 27 Feb 2006 19:52:24 -0500 Received: from mail.cokane.org ([216.196.181.22]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060228005224.SDQF14894.gx4.fuse.net@mail.cokane.org> for ; Mon, 27 Feb 2006 19:52:24 -0500 Received: (qmail 7604 invoked by uid 1000); 27 Feb 2006 19:56:11 -0500 Date: Mon, 27 Feb 2006 19:56:11 -0500 From: Coleman Kane To: Scott Long Message-ID: <20060228005611.GA7600@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> <20060227175740.GA6099@pint.candc.home> <44033D92.2020009@samsco.org> <20060227181610.GB6099@pint.candc.home> <44034201.4040304@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44034201.4040304@samsco.org> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Tue, 28 Feb 2006 01:06:27 +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: Tue, 28 Feb 2006 00:52:26 -0000 On Mon, Feb 27, 2006 at 11:16:33AM -0700, Scott Long wrote: > Coleman Kane wrote: > > > > > >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? > > > > Well, we are talking about different things here, I think. I absolutely > agree with having separate .ko files, regardless of what kernel options > or devices are specified. What I'm wondering about is when building the > tdfx driver into the kernel, does the tdfx-linux functionality come in > via an 'option' or a 'device'. If it's an 'option', does that mean that > you can load the tdfx_linux.ko module into a kernel that has the tdfx > device included? I see where you're going with this. As I recall, this was a hinderance back when I first wrote the driver (resulting in the default of TDFX_LINUX being defined in the kmod). I don't know these days, if the functionality can be divided between two kmods then I would hope one could be loaded into the kernel statically and one via kmod. > > Scott >