From: Malte Gell <malte.gell@gmx.de>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linville@tuxdriver.com
Subject: Re: [PATCH] ar9170usb: LEDs are confused
Date: Fri, 2 Oct 2009 08:52:36 +0200 [thread overview]
Message-ID: <200910020852.36427.malte.gell@gmx.de> (raw)
In-Reply-To: <200910011654.10963.chunkeey@googlemail.com>
Christian Lamparter <chunkeey@googlemail.com> wrote
> On 2009-10-01 06:32 AM, Malte Gell wrote:
> >I first noticed the LEDs are confused,
>
> no, the LED colors is not _confused_ at all.
> This is simply different on.... well, you know: on a per-device base!
Yeah, I guessed it. But, guess... i am not a real hacker so my dirty little
patch just is a trial by combat solution for my own boy ;-)
> 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. And
Neatgear sticks look ugly.
> 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?
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
Regards
Malte
next prev parent reply other threads:[~2009-10-02 6:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 14:54 [PATCH] ar9170usb: LEDs are confused Christian Lamparter
2009-10-01 18:06 ` Hin-Tak Leung
2009-10-01 20:34 ` Christian Lamparter
2009-10-01 21:24 ` Hin-Tak Leung
2009-10-01 23:18 ` Christian Lamparter
2009-10-02 10:06 ` Malte Gell
2009-10-02 6:52 ` Malte Gell [this message]
2009-10-02 10:46 ` Christian Lamparter
2009-10-02 11:45 ` Malte Gell
2009-10-02 19:08 ` Christian Lamparter
2009-10-03 2:53 ` Malte Gell
2009-10-03 11:29 ` Christian Lamparter
2009-10-03 17:28 ` Malte Gell
2009-10-02 22:25 ` Joerg Albert
2009-10-02 23:03 ` Joerg Albert
2009-10-03 0:05 ` Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910020852.36427.malte.gell@gmx.de \
--to=malte.gell@gmx.de \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).