(Previous message failed)

The Wi-Fi status LED on Acer Extensa 5220 works incorrectly.
When using b43, it is turned on only if radio is disabled.
When using ndiswrapper, it is blinking when disconnected, on when
connected and rapidly flashes when information is being sent or received.

When "/sys/class/leds/b43-phy0::radio/brightness" is set to 0, the LED
is turned on. When it is 1 to 255, the LED is off.

vi-notebook:/sys/class/leds/b43-phy0::radio# cat trigger
none ide-disk rfkill0 ADP1-online BAT0-charging-or-full BAT0-charging
BAT0-full mmc0 phy0rx phy0tx phy0assoc phy0radio [rfkill4]

If I set "/sys/class/leds/b43-phy0::radio/trigger" to "phy0rx", LED will
be turned on and off on every received packet (brightness will
alternate: first 0, then 255, then 0 and so on)

There are also b43-phy0::rx and b43-phy0::tx, but they have no physical
implementation on my device.

Should LEDs be controlled from userspace script? How to receive that
"phy0rx" and "phy0tx" events from userspace?

The following one-liner will give LED flashing similar to original:
for((;;)) { sleep 0.1; ifconfig wlan0 | perl -ne '/TX packets:(\d+)/ and
print "$1\n"'; } | perl -e '$q=0; $|=1; while(<>){ print "255\n" and
(select(undef,undef,undef,0.05) or 1) and print "0\n" and $q=$_ if
$_>$q; }' > /sys/class/leds/b43-phy0\:\:radio/brightness



_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to