LED support on ALIX, WRAP, etc.
There is now hardware support for LEDs on several embedded platforms, but there isn't much to do with them yet.
A forum user wrote (a long time ago) a daemon in C that will make tie an LED to network activity for a given interface:
It still compiles and runs on a new ALIX, so I'd like to eventually make a UI for that portion.
I was also thinking that in 2.0 we might be able to have LED1 flash when writing the config, or perhaps blink or flash a pattern when there is a system alert. (Morse code is part of FreeBSD's LED driver, you can
echo 'm...---...' > /dev/led/led3 and it will repeatedly flash that pattern.)
First try at an LED library to help control the LEDs on ALIX, WRAP, or anything that supports led(4) Part of feature #17
May be useful for notifications, startup progress indication, etc.
#4 Updated by Jim Pingle about 10 years ago
So I don't forget this later, in 2.0 I have it strobe on bootup but if there is an alert during the boot sequence the pattern gets messed up. The alerts should probably be on LED#1 anyhow.
Also, it may be a good idea to led_normalize() if it drops into interface assigment, but I need to test some more.
#5 Updated by Jim Pingle over 9 years ago
- Status changed from New to Closed
- % Done changed from 70 to 100
- Affected Version set to 2.0
I have already addressed the alert issue, and the interface assignment issue is apparently either fixed or no longer a concern (it worked when I just tried it).
Seeing as the bootup sequence and alerts are working, and the basic LED controls (and underlying library) are all there, it should be sufficient for 2.0.
The blinkled functionality for showing network activity on LEDs 2 and 3 can remain a package. It installs and runs fine on NanoBSD, I don't really see a need for it to be in the base system at this point.