linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sat, 3 Oct 2009 04:53:41 +0200	[thread overview]
Message-ID: <200910030453.42131.malte.gell@gmx.de> (raw)
In-Reply-To: <200910022108.15155.chunkeey@googlemail.com>


Christian Lamparter <chunkeey@googlemail.com> wrote
 
> If you take a look at the ledtriggers values in /sys/call/leds/
> "none rfkill0 phy0rx phy0tx [phy0assoc] phy0radio",
> you instantly see that the phyXname trigger is dynamic.

Can I change the link(s) there at any time or will the ar9170usb change it 
again? 
 
> in my opinion, finding a simple udev rule is harder than simply
> modify the driver code :-D.

That's true! I just had to exchange the words "tx" with "assoc" in the driver, 
whereas a udev rule is complicated!

Regards
Malte

  reply	other threads:[~2009-10-03  2:53 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
2009-10-02 19:08       ` Christian Lamparter
2009-10-03  2:53         ` Malte Gell [this message]
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=200910030453.42131.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).