All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Malte Gell <malte.gell@gmx.de>
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	linville@tuxdriver.com, "Hin-Tak Leung" <hintak.leung@gmail.com>
Subject: Re: [PATCH] ar9170usb: LEDs are confused
Date: Fri, 2 Oct 2009 12:46:34 +0200	[thread overview]
Message-ID: <200910021246.34699.chunkeey@googlemail.com> (raw)
In-Reply-To: <200910020852.36427.malte.gell@gmx.de>

On Friday 02 October 2009 08:52:36 Malte Gell wrote:
> Christian Lamparter <chunkeey@googlemail.com> 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

  reply	other threads:[~2009-10-02 10:46 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
2009-10-02 10:46   ` Christian Lamparter [this message]
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=200910021246.34699.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=malte.gell@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.