On Friday 02 October 2009 08:52:36 Malte Gell wrote: > Christian Lamparter <chunkeey@xxxxxxxxxxxxxx> wrote > > On 2009-10-01 06:32 AM, Malte Gell wrote: > > For example: The Netgear uses a single bi-color LED for their WNDA3100 > > stick. It glows blue or/and orange depending on the selected band and > > current operation mode and state... > > The Netgear (WN?) 111 even only has one blue LED as far as I know. the question is if it's the only device with this deficit, or not? > > FYI: you can assign the LEDs under "/sys/class/leds/" with a different > > tigger without messing with the kernel source... An up-to-date README can > > be found in the kernel's documentation directory: > > Documentation/leds-class.txt , or you can look it up online as well: > > http://www.mjmwired.net/kernel/Documentation/leds-class.txt (from 2.6.31) > > Very good to know. This needs a udev rule, right? yes, should be possible one way or another... If you do find an easy ACTION== rule, then let us know! It would make a nice addition to the wiki @ wireless.kernel.org . > But, what about a USB ID based decission in the driver how to handle the LED? > I have a Fritz WLAN N, USB ID: 057c:8401 The first post had a patch attached: http://patchwork.kernel.org/patch/50977/ (raw patch) => http://patchwork.kernel.org/patch/50977/raw/ it should do exactly what you want. just make sure, you reverted any previous LED related patch, or it will not apply cleanly. Regards, Chr -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
