On Mon, Dec 22, 2008 at 10:20 AM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > This is the first series of general cleanup to get us into > abandon our complex internal regulatory infrastructure. This is > quite a lot of work as we rely on our own internal "mode" stuff > and our own ath9k_channel heavily. > > We start this work by ditching the mode stuff where we can > and set a staging ground for us to abandon our own internal > ath9k_channel. The values which we want to actually keep from > ath9k_channel are the calibration data. Since it seems other > drivers can make use of this we add a priv section to > ieee80211_channel and start making use of this in ath9k. John, I will go back and try to redo this series without the channel->priv addition as the calibration data is band specific so in reality there should be no need to have a private section per channel for calibration that I can see so far. Additionally as Johannes has pointed out to me we should be able to index into our own tables for whatever private data later once we have a static declaration of the channels. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
