Adrian Chadd wrote: > Right, but for AP mode what's involved? > > * Does it send out a CSA to the same channel but different operational > mode stuff? > * are all current aggregation sessions maintained, or are they reset > when a CSA to the same channel is done? > * What about stuff to do with power saving? All of the above probably have to be handled. :) (along with virtual interface management). > I'm ignoring CWM for now until I've finished off these SMP TX > aggregation bugs, then I'll sort out channel scanning and power saving > stuff. That sets all the right "bits" for CWM (ie, being able to queue > all the frames without flushing them, then restarting the software TX > queue as needed.) Once that's done, CWM should be: > > * signal stop TX; > * wait for TX threads, TX completion and TX DMA to complete; > * signal a rate control change; > * recalculate the rate control selection for everything in the software queues; > * restart.. You missed the MAC/PHY update based on the new channel information. Which is where it gets tricky, since we end up doing a full reset. Sujith -- 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
