> - This option enables the hardware independent IEEE 802.11 > - networking stack. > + This option enables support for a framework used by IEEE-802.11 > + SoftMAC devices. SoftMAC devices allow for a finer control of the > + hardware, allowing for 802.11 frame management to be done in software > + for them, for both parsing and generation of 802.11 wireless frames. > + Most 802.11 devices today tend to be of this type. > + mac8011 implements the cfg80211 callbacks for SoftMAC devices, mac80211 > + mac80211 then depends on cfg80211 for both registration to the networking > + subsystem and for configuration. Configuration is handled by cfg80211 both > + through nl80211 and wireless extensions. > + > + If you have new userspace utitlities which support nl80211 you do not utilities > + need wireless-extensions to support a mac80211 device. And in any case I really don't see a need to explain the wireless configuration stuff in a Kconfig entry. IMHO the text should be short and to the point, your texts give too much background information that doesn't help anyone except people who already know about wireless stuff to make a choice. > + For more information refer the the wireless wiki entry on mac80211: > + > + http://wireless.kernel.org/en/developers/Documentation/mac80211 > + > + When built as a module mac80211 will be built as mac80211.ko, if not sure > + you should build this as a module. We do not include the '.ko' in the module name, just say "The module will be named mac80211" or so. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
