Subject: Re: firmware loading (Was: Re: iwi WiFi interface firmware load on
To: Rui Paulo <email@example.com>
From: thilo <firstname.lastname@example.org>
Date: 12/04/2005 18:18:51
Rui Paulo wrote:
>On 2005.12.03 18:44:26 +0900, Curt Sampson wrote:
>| 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.
>| 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?
>| For anybody interested, I've appended a quick (and as yet entirely untested)
>| sketch of the script; comments are welcome.
>| 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
The advantage would be, that nfs-root fs would be possible.
(even w/o firmware load, nw-keys would be missing (in the best case it
would an open system...))
Isn't there a mechanism to set things via a db in the kernel? (I think
I've seen it but don't know where).
-- would/could properties(9) be the thing to use?