Wireless LED usage during use.
|Reported by:||jg||Owned by:||rchokshi|
|Priority:||high||Milestone:||8.2.0 (was Update.2)|
|Keywords:||Cc:||jcardona, walter, marcelo, mbletsas, jg, GR-Wireless-OLPC@…, danw, dwmw2, mikus@…, mtd|
|Deployments affected:||Action Needed:||never set|
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.
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.
Change History (21)
comment:1 follow-up: ↓ 2 Changed 8 years ago by kimquirk
- Milestone changed from BTest-4 to Trial-2
- Verified unset
comment:4 Changed 8 years ago by jg
- Component changed from distro to wireless
- Milestone changed from Trial-2 to Trial-3
comment:8 Changed 8 years ago by jcardona
- Owner changed from jcardona to rchokshi
- Type changed from defect to enhancement