On Wed, Dec 21, 2011 at 05:28:11AM -0800, Stanislaw Gruszka wrote: > On Tue, Dec 20, 2011 at 11:35:16AM +0530, Yogesh Ashok Powar wrote: > > Ideally, hardware/firmware initialization is complete after the > > drv_start routine. In mac80211 restart code (ieee80211_reconfig), > > defer calling the driver commands i.e. setup fragmentation > > threshold, rts threshold and coverage class till drv_start > > routine is called. > > I think this could break drivers that could relay on order we > have at present. Also chenglog does not tell much. What for you > need that change? Is there any specific example? Currently, when the AP is initialized by the hostapd, drv_start is called first and then the mentioned commands. We should follow the same sequence even during reconfig. The reason we need these commands to be sent after drv_start is mentioned in the commit log i.e. our hw/firmware initialization gets completed in drv_start. Hence we expect these commands only after drv_start. Thanks Yogesh -- 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
