From owner-freebsd-arch@FreeBSD.ORG Wed Dec 21 13:53:04 2005 Return-Path: X-Original-To: freebsd-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 0F4FA16A41F; Wed, 21 Dec 2005 13:53:04 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76C7C43D6E; Wed, 21 Dec 2005 13:53:02 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.236.214] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1Ep4Oj1Gdm-00056M; Wed, 21 Dec 2005 14:52:56 +0100 From: Max Laier Organization: FreeBSD To: freebsd-arch@freebsd.org Date: Wed, 21 Dec 2005 14:52:57 +0100 User-Agent: KMail/1.8.3 References: <43A8EE23.3010202@errno.com> In-Reply-To: <43A8EE23.3010202@errno.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5592769.eAg4r3ncfo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512211453.03946.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Damien Bergamini , flz@freebsd.org Subject: Re: firmware loading 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: Wed, 21 Dec 2005 13:53:04 -0000 --nextPart5592769.eAg4r3ncfo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 21 December 2005 06:54, Sam Leffler wrote: > Florent Thoumie and I have been working on some generic support for > loading firmware using kld's. You can find a proof of concept at: > > http://www.freebsd.org/~sam/firmware.tgz > > It has code to manage firmware images and load them on demand by > requesting a kld through standard facilities. Firmware is packaged > using a genfw program that's included. You can package one or more > firmware images in a single kld. I've packaged the iwi firmware as a > boot image in a single kld + kld's for each operating mode that have two > firmware images. The tarball also includes modified versions of the iwi > and ipw drivers to use the code. I tested iwi, Florent is working on ipw. > > If you're interested in this stuff feel free to pick it up; I've run out > of time to work on it. There are some potential issues with holding > locks over the linker calls and the genfw program could use some TLC and > probably a new name (plus the man page needs to be completed). I am generally interested and will probably look at it between Christmas an= d=20 the New Year - unless Damien wants to look at it himself. The current sche= me=20 of loading the firmware is disfunctional with a WITNESS enabled kernel (too= =20 much "sleep while holding mutex") and needs to be fixed anyway. Is this work in perforce? Is Florent still actively working on it? > It appears ispfw can be reworked to use this code. iwi and ipw > definitely can use it. Not sure who else can/should use it. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart5592769.eAg4r3ncfo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDqV4/XyyEoT62BG0RAjwUAJ4jdTxBdo1x8Uo4nQxpQbycr7Sz7QCeOUoz AEhd1ssViHsxpbZ1LeEGEu4= =1vkc -----END PGP SIGNATURE----- --nextPart5592769.eAg4r3ncfo--