I'm in the process of modularizing the ieee80211 (Wireless LAN) code,
and would like some feedback on what the module's name should be. I can
think of at least three or four likely candidates:
net80211
ieee80211
wlan
wireless-lan
I'm leaning towards the
On Wed, Apr 25, 2012 at 05:52:31PM -0700, Paul Goyette wrote:
I'm in the process of modularizing the ieee80211 (Wireless LAN)
code, and would like some feedback on what the module's name should
be. I can think of at least three or four likely candidates:
net80211
ieee80211
I'd
I've been working on modularizing the ieee80211 code, and I've
discovered that the code using a link_set to collect various one-time
initialization routines. There is a RUN_ONCE() invocation that uses
__link_set_for_each() to iterate over these init routines.
This all works just fine when
In article 20120426013452.gl20...@pixotech.com,
David Young dyo...@pobox.com wrote:
On Wed, Apr 25, 2012 at 05:52:31PM -0700, Paul Goyette wrote:
I'm in the process of modularizing the ieee80211 (Wireless LAN)
code, and would like some feedback on what the module's name should
be. I can think
link set won't work for modules. ISTR pooka@ did a work-around for
RUMP or whatever.
(Ideal alternative is decent ctors/dtors support.)
On Thu, Apr 26, 2012 at 11:44 AM, Paul Goyette p...@whooppee.com wrote:
I've been working on modularizing the ieee80211 code, and I've discovered
that the
I thought module names alway match what's define'ed in config(1) files...
... and now I've found it's wlan, which should be changed to a saner
name like net80211.
On Thu, Apr 26, 2012 at 9:52 AM, Paul Goyette p...@whooppee.com wrote:
I'm in the process of modularizing the ieee80211 (Wireless
Yes, wlan was my first choice, cimply because that is the name of the
config attribute.
But it seems a consensus is emerging that the module name should be
net80211 so that's what I'm going to do (assuming I figure out the
link_set issue).
I'll leave the rototilling of the config files for
On Sep 16, 7:17am, Masao Uebayashi wrote:
}
} I thought module names alway match what's define'ed in config(1) files...
At this time, config(1) has absolutely nothing to do with
modules. There is a movement afoot to change that. I'll just say that
I don't agree with changing that, but I
Is this a NetBSD issue, or something else?
load averages: 7.99, 7.94, 7.91; up 0+21:43:0721:25:56
34 processes: 2 runnable, 24 sleeping, 8 on CPU
CPU0 states: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle
CPU1 states: 0.0% user, 100% nice, 0.0%
