On Tue, Dec 8, 2009 at 8:06 AM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Tue, Dec 08, 2009 at 08:01:52AM -0800, Luis R. Rodriguez wrote: >> On Tue, Dec 8, 2009 at 6:57 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: >> > On Mon, Dec 7, 2009 at 4:59 PM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: >> >> On Mon, Dec 07, 2009 at 12:05:54PM +0200, Shahar Or wrote: >> >>> Adds support for the WiFi activity LED on the Dell Vostro A860 laptop. >> >>> >> >>> Signed-off-by: Shahar Or <shahar@xxxxxxxxxxxxxxx> >> >>> --- >> >>> I hope this one is perfect. >> > >> > Thanks for the patch. As for getting a better solution to LEDs, I >> > trolled through the ACPI spec and code, and while various modules >> > do set up LED pins, there doesn't seem to be a way to generally >> > get that information from another module and it appears different >> > between each vendor. I am by no stretch expert in ACPI stuff >> > though. >> > >> > Luis, I've asked this before but maybe you know better now or know >> > whom to ask on your side. Atheros must have a way on Windows to >> > figure out the LED pin/polarity -- do you have any idea? Ath9k >> > uses the SREV but that seems to be insufficient for ath5k judging >> > by all the quirks. >> >> IIRC this is all mapped in the INF file, I thought I had released an >> INF file under the ISC license but it seems that's not the case, I can >> try to do that if it helps. Anyway, if we can move this sort of map to >> userspace it'd be neat as you'd just need a userspace file update. >> Only thing is how to do this in a generic way for all wireless drivers >> and if this is indeed useful for other drivers. > > Export something through sysfs and use a udev rule? True. Is sysfs the preferred fs nowadays, what about configfs? Or maybe even udev rule --> nl80211 ? Luis -- 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
