Mohammed Shafi Shajakhan <mshajakhan@xxxxxxxxxxx> writes: > From: Mohammed Shafi Shajakhan <mshajakhan@xxxxxxxxxxx> > > This reverts commit 0ce3bcfc84900a64347b0fe1140229bd81314008. > > Event though with the above commit we obtain the configured DTIM period > from the AP rather than always hardcoding it to '1', this seems to cause > problems under the following scenarios: > * Preventing association with broken AP's How can different dtim value cause problems with association? Power save should not be even enabled during association. Or do you mean there are problems after association, for example during eap negotation? > * Adds latency in roaming We should try to solve this problem differently than hardcoding dtim. There are other ways to trigger roaming than just following beacons. And if there's no data, there's no need to roam either. I have been hoping to work on improving roaming, but never found the time to do it :/ > So its better to always use the safe value of '1' for dtim period By hardcoding dtim you increase the power consumption in the case when there is no data traffic, so it's not definitely better in all cases. I would prefer to fix the real issues instead of hardcoding dtim. And if it's really essential to hardcode it now, please add a big fat warning indicating that this is a temporary solution and should be fixed properly without hardcoding anything. -- Kalle Valo -- 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
