Johannes Berg wrote:
Would you actually need a fully refcounted enable/disable?

No, we could stick with our existing setup if the stack did something different.

Because for
the stack it wouldn't be required if it'd simply not start scanning when
queue is disabled and stop scanning immediately when queue stop is
requested.

That would work, assuming there is a way to make the stack listen for the "TX queue stopped" event (or would the ieee80211_tx_disable wrapper take care of that?).

Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to