On Thu, 2008-09-25 at 12:57 -0400, Dan Williams wrote: Let me elaborate a bit on what my patch does > 2) common GIWSCAN processing function that takes a list of common BSS > structures that the driver stores internally. The common BSS structure > would have a "void *driver_data" pointer in which the driver could keep > driver-specific data items, I actually am allocating space for it in the same struct, rather small difference though. > but the driver would be responsible for > setting all available information in the common BSS structure when the > firmware provides scan results. lib80211 provides common allocation, > deallocation, bss entry aging, ref/unref, and free-list fetching. What cfg80211 with my patch does is bind it to the wiphy, which you really want to have anyway when taking advantage of the regulatory stuff etc. It's currently not providing any deallocation function, but is providing allocation (currently only based on a beacon/proberesp frame but a new version can be provided), entry aging, ref/unref. List fetching is notably absent, I was thinking an iterator function should be provided if at all necessary, maybe the "find me an entry with these characteristics" functions should just be expanded to have more optional parameters. Then again, you may need to make decisions based on security etc. I have not so far thought about splitting out the information and stuffed it all into an information element list that I'm internally handling, for speed the SSID IE should probably be pointered explicitly though. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
