Hi all, the OSLL guys and me had started implementing the IEEE 802.11s powersave schemes in mac80211. We currently have power mode indication and state tracking and are working on powersave frame buffering and mesh synchronization. A next topic will be to put the hardware to sleep to actually save energy. Until now we only implemented in mac82011. I looked through mac80211 and ath9k and am unsure, how to actually manage sleep and wakeup in the mesh context. Maybe I should give a brief introduction to IEEE 802.11s powersave here: - Each node has to send its own beacon - Power mode is not global, but link-specific - 3 power modes: active, light sleep, deep sleep - active = always on - light sleep = wake up for the neighbors beacon - deep sleep = only wake up for sending own beacon So the critical point here is, that we need to put the hardware to sleep but wake up for: - sending own beacon - TBTT of all neighbors towards we are in light sleep (or maybe all neighbors as proof-of-concept) so it is a mixture of ad-hoc , station code and completely new stuff. So, driver developers (I am especially looking at the ath9k guys), is it actually possible to send beacons, to have powersave in between and to wake up for scheduled events? Regards Marco Porsch PS: A better explanation and a nice example of IEEE 802.11s powersave is given here: http://dl.dropbox.com/u/31741282/11s_powersave.pdf -- 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
