Re: wireless: recap of current issues (configuration)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Stuffed Crust wrote:
The hardware knows what frequencies it supports. Unfortunately this has to be a somewhat dynamic thing, as this is often not queryable until the device firmware is up and running. This can be accomplished by passing a static table to the register_wiphy_device() call (or perhaps via a struct wiphy_dev parameter) or through a more explicit, dynamic interface like:

wiphy_register_supported_frequency(hw, 2412).


For completely programmable hardware, the stack should interact with a module like ieee80211_geo, to help ensure the hardware stays within legal limits.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux