On Thu, 2008-09-11 at 23:35 +0300, Jouni Malinen wrote: > Johannes Berg wrote: > > The beaconing API in total is a bit strange, we tell the driver when the > > beacon changes and it can then request one, but we never tell it when to > > start/stop beaconing, which means that currently your driver has to > > figure to start out beaconing on the first beacon change, and then > > cannot possibly stop again... We can return NULL from the beacon get > > function but that could be an error condition too... > > The original design was for AP mode only and the assumption was that > Beacon transmission is enabled pretty much all the time. Returning NULL > was used if ever needed to stop Beacon transmission for some period of > time. That can only work with some hardware though, if the hardware doesn't beacon from a template. > > I think we just need to add start/stop beacon bits, and then we can use > > them around a scan too, thoughts? > > That sounds reasonable. I'll take a look sometime. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
