[PATCH 0/3] WLAN/SDIO power up/down synchronization

Andy Green andy at openmoko.com
Sat Nov 22 11:03:51 CET 2008

Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> Association is presumably lost because the firmware in the Atheros
|> module is directly seeing this "go down", "come back up from scratch"
|> traffic.
| The module actually has to be reset for letting the SDIO stack
| rediscover it. The SDIO spec allows the usual detection process
| only after a power-on reset (or, in our case, pulling the reset
| line) or a soft reset (where you set a bit to reset the IO
| function).

OK, it's not willing to do the "come back up from scratch" stuff
demanded by the stack until reset but it means the same.

|> It's fine for now, It's no worse than normal soft MAC device under Linux
|> where mac80211 is down in suspend and association is lost:
|> NetworkManager or similar will reacquire it on resume.
| Oh, good. Does it also set ESSID, encryption, and such again ?
| That would make things very easy for me ;-)

Yes on normal laptop NetworkManager it does IOCTL or whatever for iwlist
wlan0 scan, and then if it likes an AP for normal WPA case it uses
wpa_supplicant so everything is redone.  I don't use WEP but I am sure
this is also handled by NetworkManager.

Since the user may often suspend in one locale and resume in another,
this has to be the way to come at it.

I don't know the status of NetworkManager-type support in the rootfs-es,
presumably Debian has the real thing but how well it integrates with
AR6001 I dunno.  There was talk about various other NM-alikes over the
months but all I ever saw was failure to get iwlist-type results from
any UI... but I only check the distro UIs sporadically.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list