On Fri, 2010-06-25 at 18:01 +0200, Helmut Schaa wrote: > Am Donnerstag 24 Juni 2010 schrieb Johannes Berg: > > b) You need to get a new beacon frame from mac80211 only when it > > changes. You can do this from set_tim(). HOWEVER: since you're not > > getting a new one from mac80211 all the time anyway, you NEED to > > have the driver or firmware overwrite the DTIM count, like b43's > > firmware for example will do. > > And the broad- and multicast buffering also needs to be done in the driver > (when the fw/hw cannot handle it) as mac80211 uses its own DTIM count for > deciding when to "release" buffered frames to the driver. Well, yes, but I don't get it. Are you trying to conjure a third way of doing things? How would you like it to work? I don't understand why you expect to have a correct DTIM count field when you don't pull every beacon from mac80211. If you pull each beacon it's all correct. If you don't, you need to take care of everything DTIM related, there's simply no way to do it differently. Does your device fill the DTIM count field or does it not? That's really the only thing you need to know, no? johannes -- 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
