From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 25 12:24:25 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C22E16A41C for ; Sat, 25 Jun 2005 12:24:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD98343D4C for ; Sat, 25 Jun 2005 12:24:24 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j5PCOLGG043532; Sat, 25 Jun 2005 21:54:22 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Sat, 25 Jun 2005 21:54:17 +0930 User-Agent: KMail/1.8 References: <200506251203.13569.sebastien.b@swissinfo.org> In-Reply-To: <200506251203.13569.sebastien.b@swissinfo.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1279585.YzMc3188s8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200506252154.18242.doconnor@gsoft.com.au> X-Spam-Score: -2.4 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: Seb Subject: Re: Accessing filesystem from a KLD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jun 2005 12:24:25 -0000 --nextPart1279585.YzMc3188s8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 25 Jun 2005 19:33, Seb wrote: > How can I access the filesystem from a kernel module ? > In fact, I want my device driver to retreive a firmware image stored on t= he > filesystem (instead of putting the firmware data in a static array at > compile-time) for memory usage and legal concerns. Blocking calls are OK. > I have searched the manpages and the web, but I haven't found anything > relevant. if_ndis does this (well ndis) to load firmware images from the file system = for=20 drivers. I wonder if it would make sense to generalise it - the ndis code covers thi= ngs=20 like building the firmware image into the kernel for cases where you are NF= S=20 mounting your disks (for example). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1279585.YzMc3188s8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBCvUzy5ZPcIHs/zowRAoFbAJ4smOYx7gD5FJHeolLQLh6wecYsWwCfR4Zu w/Z73/sQhDPlsjVqJpP9bA0= =fc87 -----END PGP SIGNATURE----- --nextPart1279585.YzMc3188s8--