LED Assocation indication behavior changed

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4539

mrjoel

04-01-2008 19:22:37

With the mainline kernel adoption of the rt2x00 driver, I'm trying to migrate to it from the legacy rt2570 driver.

I have a minor issue and clarification on a behavior change between the two drivers.

I have a Gigabyte GN-WBKG USB interface which has four LEDs on one row that indicate power being applied on the USB bus and nothing else. There is a second row with two LEDs, one of which indicates network activity, and the second which, under the old driver indicated a successful association, but under the new driver only indicates that the module is loaded.

I haven't yet gotten traffic to successfully pass, but I assume that the activity LED will have the same behavior with the new driver. My question is whether the second LED was chosen to have the new behavior as a design point, or not. I would rather have the behavior that existed under the old driver.

IvD

04-01-2008 19:30:31

The current behavior is a bug, I have recently reworked the LED handling to something completely new.

I'll see what I can do about it to make it return to the correct behavior.

IvD

06-01-2008 14:14:44

I have updated the LED handling, it should be correct now.

mrjoel

06-01-2008 16:09:33

Great - thanks!

(I'll actually test it once we get the authenticate timed out issues resolved.)

mrjoel

04-03-2008 04:35:38

I'm still seeing the behavior described at the beginning of this thread. I can't get the driver to associate, but as soon as I issue an 'ip link set wlan0 up', the LED lights right up.