On Sun, 2008-10-19 at 14:00 +0300, Kalle Valo wrote: > > Then add a new flag to mac80211 hw description that says "driver will > > watch beacons". This means that the code above that rearms the timer for > > the future 'nothing from AP' check is skipped. > > I will. I need to check that if the "firmware beacon watch" is enabled > only when PSM is enabled. If it is, we might have to make the flag > dynamic. IIRC it's a separate flag. > > Also add a way for mac80211 to tell the driver after how many beacons > > (or calculate the timeout in ms, it's convertible) it should tell > > mac80211 about the situation. Finally, to make it possible to have the > > driver tell mac80211, extend the MLME callback (ieee80211_notify_mac) > > The beacon filtering in stlc4560 works so that a beacon is passed to > the host only when the TIM bit for the AID is set. There's also a beacon checksum feature which we might want to enable, just in case the AP ever changes QoS parameters etc. > There isn't any > timeout for delivering beacons to the host, if the data path is idle > for 24 hours, mac80211 will not receive any beacons for the 24 hours. > I don't see why we need a timeout here. Right. But we need to program the chip to tell the chip "hey please tell me if you haven't seen a beacon in X seconds". > I believe that there's also a feature in stlc4560 that the driver can > provide a checksum of the beacon and the firmware will send the beacon > if checksum doesn't match. But I don't yet know how that works in > practise. It seems to be a firmware feature, first beacon from the BSS the firmware computes the checksum, and if it changes it lets the beacon go through and re-computes the checksum, so you see all beacon changes. Maybe it excludes the TIM. I think we want this for when the QoS parameters or something else changes. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
