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, "Hin-Tak Leung" <hintak.leung@gmail.com>
Subject: Re: [PATCH] ar9170usb: LEDs are confused
Date: Fri, 2 Oct 2009 13:45:55 +0200 [thread overview]
Message-ID: <200910021345.55567.malte.gell@gmx.de> (raw)
In-Reply-To: <200910021246.34699.chunkeey@googlemail.com>
Christian Lamparter <chunkeey@googlemail.com> wrote
> > 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?
Is it feasable to write to the well known stick makers (Netgear, AVM,
Belkin,Asus...) and just ask them?
>
> > > FYI: you can assign the LEDs under "/sys/class/leds/"
> > 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!
Do I hear irony? Is it not easy? Isn't it just a link that needs to be made /
changed? Does it matter, when to do this, e.g. after the module ist loaded or
the network system is started?
> > 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/
Have not tried it, is it well tested? If it works, will the patch become
official part of compat-wireless?
Regards
Malte
next prev parent reply other threads:[~2009-10-02 11:45 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
2009-10-02 11:45 ` Malte Gell [this message]
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=200910021345.55567.malte.gell@gmx.de \
--to=malte.gell@gmx.de \
--cc=chunkeey@googlemail.com \
--cc=hintak.leung@gmail.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).