From owner-freebsd-arch@FreeBSD.ORG Mon Nov 21 18:44:47 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 4069116A41F for ; Mon, 21 Nov 2005 18:44:47 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5B7E43D45 for ; Mon, 21 Nov 2005 18:44:46 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id jALIibWL028804; Mon, 21 Nov 2005 13:44:37 -0500 (EST) Date: Mon, 21 Nov 2005 13:44:37 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Warner Losh In-Reply-To: <20051121.113052.71133065.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) 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 Reply-To: Daniel Eischen 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:44:47 -0000 On Mon, 21 Nov 2005, Warner Losh wrote: > > 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. Not taking one side or the other... Can we use a common tool to convert firmware to a kld? Just pass it the symbol name or whatever else you need? I guess this makes the assumption that most firmware consists of just one object file. -- DE