Adrian Bunk wrote :
>
> Using WIRELESS_EXT instead of CONFIG_NET_RADIO is simply ugly.
Sorry, but I did not see this e-mail in my inbox. Maybe my
spam filter is too agressive. I would prefer that to the
alternative...
You are probably right that something need to be done about
it, but I believe this is the wrong direction. I would prefer you to
replace WIRELESS_EXT with CONFIG_WIRELESS_EXT.
Historically, CONFIG_NET_RADIO has always been the option to
enable WLAN drivers. The same way CONFIG_NETDEVICES enable all network
drivers.
A long time ago, I did abuse CONFIG_NET_RADIO to also enable
Wireless Extensions. Not being totally happy about it, I try to
minimise to use of CONFIG_NET_RADIO in the *generic* network code so
that we could revert that easily. Now is probably the time.
Kernel 2.6.14 introduce a generic 802.11 stack in the
kernel. This stack depends on Wireless Extensions. Now we have the
messy situation of having a generic network component that depend on a
driver option and enables it.
I propose that Wireless Extension have it's own separate
CONFIG_WIRELESS_EXT. Both CONFIG_NET_RADIO and CONFIG_IEEE80211 would
depend on it and enables it.
What do you think of that ?
Jean
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
