From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Add radio led trigger
Date: Mon, 7 Jan 2008 19:44:04 +0100 [thread overview]
Message-ID: <200801071944.05063.IvDoorn@gmail.com> (raw)
In-Reply-To: <1ba2fa240801061514m9c58b15g1ed1455e807a28b6@mail.gmail.com>
On Monday 07 January 2008, Tomas Winkler wrote:
> On Jan 6, 2008 8:25 PM, Ivo van Doorn <ivdoorn@gmail.com> wrote:
> >
> > On Sunday 06 January 2008, Tomas Winkler wrote:
> > > On Jan 6, 2008 3:10 PM, Ivo van Doorn <ivdoorn@gmail.com> wrote:
> > > > Some devices have a seperate LED which indicates if the radio is
> > > > enabled or not. This adds a LED trigger to mac80211 where drivers
> > > > can hook into when they are interested in radio status changes.
> > > >
> > > >
> > > I wonder how this go together with RF KILL led?
> >
> > They would be competing I fear, but not all devices have a rfkill button,
> > which makes the mac80211 radio led trigger more usefull I think.
> >
> What inquires me is in the following snippet is would you lit the
> led if even if rfkill HW switch is on?
> --- a/net/mac80211/ieee80211.c
> +++ b/net/mac80211/ieee80211.c
> @@ -219,6 +219,7 @@ static int ieee80211_open(struct net_device *dev)
> if (res)
> return res;
> ieee80211_hw_config(local);
> + ieee80211_led_radio(local, 1);
> }
>
Good point. I have updated the patch to make it check the radio_enabled
configuration parameter.
Ivo
next prev parent reply other threads:[~2008-01-07 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 13:10 [PATCH] mac80211: Add radio led trigger Ivo van Doorn
2008-01-06 18:19 ` Tomas Winkler
2008-01-06 18:22 ` Michael Buesch
2008-01-06 18:25 ` Ivo van Doorn
2008-01-06 23:14 ` Tomas Winkler
2008-01-07 18:44 ` Ivo van Doorn [this message]
2008-01-07 18:45 ` [PATCH v2] " Ivo van Doorn
2008-01-09 0:18 ` Tomas Winkler
2008-01-09 16:50 ` Ivo van Doorn
2008-01-09 17:07 ` Tomas Winkler
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=200801071944.05063.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@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).