Subject: firmware loading (Was: Re: iwi WiFi interface firmware load on boot)
To: Curt Sampson <cjs@cynic.net>
From: Rui Paulo <rpaulo@fnop.net>
List: current-users
Date: 12/03/2005 19:40:16
--NPukt5Otb9an/u20
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.12.03 18:44:26 +0900, Curt Sampson wrote:
|=20
| This is going to the current-users list because I feel that the people
| here are probably best qualified to answer this. But please cc me on
| responses if you wouldn't normally, as I'm not on the list itself.
|=20
| I'm consing up an rc.d script to load up the firmware for an iwi network
| interface, so that dhclient can work immediately on boot. However, I need
| a name for the darn thing. I'm thinking "iwisetup," but does anybody have
| a better idea?
|=20
| For anybody interested, I've appended a quick (and as yet entirely untest=
ed)
| sketch of the script; comments are welcome.
|=20
| Oh, I'm developing this on a 3.0_BETA system, if there's some reason
| this wouldn't work on -current, can someone let me know? I can't
| off-hand think of any obvious way to be able to easily switch between
| netbsd-3 and current on my laptop.

I think that instead of creating a rc.d script for every firmware, we
should try to let the kernel do that automatically like Linux does
with hotplug. And this should work for every driver.

What do you think ?

		-- Rui Paulo

--NPukt5Otb9an/u20
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDkfSgZPqyxs9FH4QRArHZAJ9K2oGxez/8V49qNKxkdp9wOizHbQCbB2dy
aRZ1yhT2IbUWP9xB0fQn+9A=
=fptN
-----END PGP SIGNATURE-----

--NPukt5Otb9an/u20--