On Thu, Oct 20, 2011 at 11:11 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2011-10-20 at 11:08 -0700, Thomas Pedersen wrote: >> On Thu, Oct 20, 2011 at 11:03 AM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >> > On Thu, 2011-10-20 at 10:56 -0700, Thomas Pedersen wrote: >> > >> >> >> I'm not sure what you mean, this is the only way to get the WMM >> >> >> parameters? Usually these are just set with ieee80211_set_wmm_defaul() >> >> >> on bringing up the interface. >> >> > >> >> > Right, but >> >> > a) if you're using just the default, no need to derive from the default >> >> >> >> The user might wish to customize the queue parameters though. >> >> >> >> > b) should they be changeable? >> >> >> >> Why not? >> > >> > Well there no API for it now, is there? >> > >> >> NL80211_ATTR_WIPHY_TXQ_PARAMS? > > Oh, hmm. Ok I guess that's allowed on mesh -- but when it changes you > won't update IEs? > We reconstruct IEs on every beacon_get() (I know...), so it should be OK. Thomas -- 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
