Messages in this thread | | | Date | Sat, 14 Jan 2006 17:07:01 -0500 | From | Jeff Garzik <> | Subject | Re: wireless: recap of current issues (configuration) |
| |
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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |