> Just to sum up the issue for Johannes: Stefano's patch adds per-rate > information to the PID algorithm state. This is fine, however we need to > make sure the rate control algorithm gets reinitialized when the number > of rates changes (i.e. due to a mode change, what about about regulatory > domain changes?), as otherwise we might be indexing array entries we > don't have allocated. Now this spawned the more general discussion about > when the stack should allow changing modes etc. Thanks. > So let's go back to the original issue: Johannes, can we assume rate > control always gets reinitialized when the number of rates or even the > hardware mode is changed? I have no idea. Doesn't it get initialised when the interface is brought up, and as such it would because those changes can only be done when it's down? If we want to be strict and allow changes while it's not associated but up then I think the answer is a clear no. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
