From owner-freebsd-arch@FreeBSD.ORG Wed Dec 21 17:12:31 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 98FFC16A41F; Wed, 21 Dec 2005 17:12:31 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34DA843D55; Wed, 21 Dec 2005 17:12:31 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.198] ([10.0.0.198]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBLHCRiE023576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 09:12:30 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43A98D3E.6080701@errno.com> Date: Wed, 21 Dec 2005 09:13:34 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Max Laier References: <43A8EE23.3010202@errno.com> <200512211453.03946.max@love2party.net> In-Reply-To: <200512211453.03946.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Damien Bergamini , flz@freebsd.org, freebsd-arch@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 17:12:31 -0000 Max Laier wrote: > 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 and > the New Year - unless Damien wants to look at it himself. The current scheme > of loading the firmware is disfunctional with a WITNESS enabled kernel (too > much "sleep while holding mutex") and needs to be fixed anyway. I can't recall if that's the driver's lock being held over linker calls that are potentially blocking, but if you can resolve this then I can also re-enable dynamic loading of 802.11 crypto modules. > > Is this work in perforce? Is Florent still actively working on it? It's not in perforce. Florent has already responded. > > >>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. > >