#10232 BLOC 10.1.2: WiFi dies on suspended XO-1, os300

[Zarro Boogs per Child]

#10232: WiFi dies on suspended XO-1, os300
------------------------------------+---------------------------------------
           Reporter:  hal.murray    |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  blocker       |   Milestone:  10.1.2       
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by sascha_silbe):

 Replying to [comment:11 cjb]:
 > I wonder if there's any way to detect that we had association before and
 don't have it now, after resume.  If we ask the driver for details of the
 association (like signal strength etc) does it just lie to us?
 The kernel driver will "lie" because it doesn't know better: the firmware
 doesn't inform the host about the state change and there doesn't seem to
 be a way to explicitly query the current state.
 The only idea I had so far is telling the firmware to associate again
 right after resume. AFAICT all required information is cached in the
 private driver structures. I'll attach a WIP patch to do that - I don't
 remember if it even compiled (it's been a few weeks since I last worked on
 it), but at least it should give some idea of how I intended it to work.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10232#comment:12>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system