summaryrefslogtreecommitdiff
path: root/cesar/bsu/stub/src/bsu.c
diff options
context:
space:
mode:
authorYacine Belkadi2013-04-03 11:40:24 +0200
committerYacine Belkadi2013-05-22 10:53:39 +0200
commita5821e5b218bb56400f0ef888a47ad9651484df2 (patch)
tree437a321c2d80f4afe18e72d5f1e206085f28599b /cesar/bsu/stub/src/bsu.c
parent46b9d84d9dfca1a27cea6f3b85af148cd72a2434 (diff)
cesar/{bsu,{cp/{av,}/beacon}: in the cp, use the KCCD value maintained by the bsu
On a Sta, when no beacon was received, the cp updated the KCCD value in cp_beacon_countdowns() according to the number of beacon periods elapsed since its last run. The problem is that the number of elapsed beacon periods is tricky to determine reliably. Considering that: - The bsu already maintains the value of KCCD on its own. - The changes introduced by a previous commit made the bsu send a fake beacon when an expected beacon is not received. Then make the bsu pass its value of KCCD to the cp via the fake beacon. This way, the cp won't have to determine how much beacon periods it missed. It will just have to process n fake beacons if it missed n beacon periods. In addition, this allows to centralize key change related code in one place (cp_beacon_process_bmi_eks()).
Diffstat (limited to 'cesar/bsu/stub/src/bsu.c')
0 files changed, 0 insertions, 0 deletions