Sander van Grieken sander at
Wed Jan 7 14:24:31 CET 2009

On Wednesday 07 January 2009 14:11:41 Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wednesday 07 January 2009 13:44:36 Andy Green wrote:
> |> Somebody in the thread at some point said:
> |> |> Thanks for the report about it, what does enabled or disabled mean
> |> |> for Wifi?  Say if it is in "disabled" situation, what does that look
> |> |> like?
> |> |
> |> | eth0 is up but lost its IP, wireless is not associated.
> |> | An 'ifup eth0' immediately re-establishes the connection..
> |>
> |> I think this is actually OK if we lose association while down.  It
> |> should be a matter for the userspace stuff like NetworkManager to try to
> |> reacquire.
> |>
> |> If you think about case where it suspends and then you walked to another
> |> building before waking it, you're going to need a fresh management
> |> action of WLAN connection.
> |
> | True, but still the behaviour should be the same after every suspend
> cycle.
> I'd agree, but if there is a NetworkManager thing taking care of
> business in userspace as there should be, it will also cover this case.

Hmm.. not sure if I agree here. IMO resume should reinstate the situation as 
it was at suspend. NM or any userspace process could then decide what to do if 
it notices the AP has disappeared.

Also I'm not a big fan of NM (yet) and usually use the old ifup/ifdown 

> ~ I don't have much idea where the toggle behaviour is coming from, but
> it can be the AR6001 firmware or SDIO stack action during suspend or both.

It's not the firmware. It started after I switched to 2.6.28 and the newer 


More information about the devel mailing list