From owner-freebsd-current Wed Dec 2 21:45:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02197 for freebsd-current-outgoing; Wed, 2 Dec 1998 21:45:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02192 for ; Wed, 2 Dec 1998 21:45:28 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA05315; Thu, 3 Dec 1998 00:44:10 -0500 (EST) Date: Thu, 3 Dec 1998 00:44:10 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812030213.SAA03115@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Mike Smith wrote: > It would certainly be feasible to arrange for the firmware images to > be loaded from separate files, should that be an acceptable > alternative. I'm open to suggestions on how to make this economical > and robust... Ooh! Ooh! Me Me! I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware image for support of RAM based TMS380 cards. In addition, some each particular card may have specific firmware it wants loaded. I'm looking for some way to load a really basic config file to let the driver know which image goes with which card. Doing this from userland isn't good as I can't do much with the card until the firmware is loaded. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message