From owner-freebsd-questions Fri Apr 5 10:50:26 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 0B21037B41C; Fri, 5 Apr 2002 10:50:06 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g35ImZS05537; Fri, 5 Apr 2002 10:48:35 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200204051848.g35ImZS05537@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: "Kreider, Carl" , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: read a file from a driver In-reply-to: Your message of "Wed, 03 Apr 2002 12:59:28 PST." <3CAB6D30.7CDAFB80@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Apr 2002 10:48:35 -0800 From: Michael Smith Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > For drivers which must be active in the boot path, it is > generally necessary to embed the firmware in the driver as > data. This is what FreeBSD does for the Adaptec SCSI > drivers. > > For drivers that need to be active after boot time, but before > the mi_startup() is complete, you can load the data in a module > that contains the data. THis is similar to compiling the data > into the kernel, but puts it at a minor level of abstraction. These two are the same case. See eg. the isp_fw module. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message