Comment 5 for bug 708776

I doubt there's very much to do about this at the kernel level, given that it's the wl driver (a closed source driver).

Note that there is a patch up for review upstream for wpasupplicant, which we're considering, in bug 638303. While this is a rather important issue for ConnMan, I suspect it may be visible here to a lesser degree for other users of wpasupplicant. I'll comment back here when the patch is in wpasupplicant in Natty to ask for testing.

Please note however that 25 seconds, while high-ish, doesn't seems like an unreasonable amount of time to wait for all the moving parts to get ready (poking the driver takes time, so does scanning...), especially after resume. Even patching wpasupplicant might not change much, especially considering the wl driver (which we can't control).