#1385 HIGH Trial-3: Wireless LED usage during use.

[Zarro Boogs per Child]

#1385: Wireless LED usage during use.
-----------------------+----------------------------------------------------
  Reporter:  jg        |       Owner:  dcbw   
      Type:  defect    |      Status:  new    
  Priority:  high      |   Milestone:  Trial-3
 Component:  wireless  |     Version:         
Resolution:            |    Keywords:         
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by rchokshi):

 * cc: GR-Wireless-OLPC at marvell.com (added)

Comment:

 Replying to [ticket:1385 jg]:
 > During a discussion of the leds intended for wireless use (and after
 much moaning and dislike of "blinkn lights" that are distracting so near
 the screen, we came up with the following scheme:
 >    1) use one LED (maybe the !), to indicate association *and*
 connectivity via infrastructure mode.
 >    2) use the other to indicate similar association *and* existence of a
 mesh portal.

 You mean mesh point here, right?

 >    3) if neither is lit, then you are trying to use a mesh that is not
 connected.
 >    4) if both are lit, then you know you are a mesh portal for a mesh.
 >
 > This would make both driven by NetworkManager rather than directly from
 firmware or the OS.  Dan thought this was already likely possible.
 >
 > A further thought occurred to me: it might be that these lights blinking
 during the attempts to establish connectivity would be one way to indicate
 progress in the algorithms for establishing connectivity.

 I could not get the precise meaning of “…association *and* connectivity
 …”. Does connectivity mean assigning IP address to that interface or is
 connectivity at L2? We are assuming the latter.

-- 
Ticket URL: <https://dev.laptop.org/ticket/1385#comment:5>
One Laptop Per Child <http://laptop.org/>