The following reply was made to PR kern/32342; it has been noted by GNATS.

From: Rui Paulo <rpaulo@fnop.net>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org, plunky@rya-online.net
Subject: Re: kern/32342: OpenBSD firmware loading framework
Date: Tue, 20 Dec 2005 01:17:44 +0000

 On 2005.12.20 01:05:03 +0000, matthew green wrote:
 | The following reply was made to PR kern/32342; it has been noted by GNATS.
 |=20
 | From: matthew green <mrg@eterna.com.au>
 | To: Iain Hibbert <plunky@rya-online.net>
 | Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
 | 	netbsd-bugs@netbsd.org, gnats-bugs@netbsd.org
 | Subject: re: kern/32342: OpenBSD firmware loading framework=20
 | Date: Tue, 20 Dec 2005 12:02:14 +1100
 |=20
 |    =20
 |     1. It seems to me that it would be better to read such a firmware fil=
 e one
 |     time and free it after use than to waste a chunk of memory (even if p=
 aged
 |     out) for ever.
 |     u
 | =20
 |  some drivers need to reload the firmware "semi-often".  ie, when
 |  my iwi(4) craps out, reloading the firmware fixes it usually.  so
 |  getting rid of it isn't always isn't a good idea.
 
 Yeah, but right now you do this manually with the iwi driver. Think
 about a firmware loading API that could be called by iwi when it craps
 out.
 
 		-- Rui Paulo