From owner-freebsd-arch@FreeBSD.ORG Mon Nov 21 18:33:05 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D28216A420 for ; Mon, 21 Nov 2005 18:33:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05E8243D49 for ; Mon, 21 Nov 2005 18:33:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jALIUqrI044333; Mon, 21 Nov 2005 11:30:52 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 21 Nov 2005 11:30:52 -0700 (MST) Message-Id: <20051121.113052.71133065.imp@bsdimp.com> To: scottl@samsco.org From: Warner Losh In-Reply-To: <43821134.6040306@samsco.org> References: <4381FEDF.7080607@root.org> <20051121.111955.74713410.imp@bsdimp.com> <43821134.6040306@samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 21 Nov 2005 11:30:52 -0700 (MST) Cc: arch@freebsd.org, nate@root.org Subject: Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 18:33:05 -0000 > Making the driver aware of the filesystem layout is a bad idea. Your opinion has been noted. Repeating it often isn't going to help. It has its advantages from the user point of view (I put a file here and it is used, my tool of choice can always be "cp"). > Encapsulating data into a KLD is not hard to do. Neither is a dozen other things that we do automatically for the user. From a user point of view this is a pita. I put this file here, and then I have to remember which magic tool to run to convert the iwi firmware into a kld. But that's a different tool from the wi driver and that's different from the iwp driver, etc. Each approach has its pro's and con's. Getting dogmatic about 'X is a bad idea, therefor you must do Y' without looking at why 'Y' might be a worse alternative to 'X' isn't going to help this discussion. Warner