From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Marcel Holtmann <holtmann@linux.intel.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
Tomas Winkler <tomasw@gmail.com>,
linux-wireless@vger.kernel.org, yi.zhu@intel.com,
Dan Williams <dcbw@redhat.com>
Subject: Re: iwlwifi - rfkill only works if the interface is up
Date: Mon, 1 Dec 2008 22:50:36 +0100 [thread overview]
Message-ID: <200812012250.37587.helmut.schaa@gmail.com> (raw)
In-Reply-To: <20081201211231.GC3479@tuxdriver.com>
Am Montag, 1. Dezember 2008 schrieb John W. Linville:
> FWIW, I'm not sure what the point of checking rfkill state would be if the
> adapter is down anyway. Hmmm...maybe management of the rfkill LED?
The main intention was that user space programs might want to listen to rfkill
events in order to bring the interface up once the killswitch is disabled.
AFAIK NetworkManager takes an interface down once it recognises that the
device is disabled through a killswitch. If the device is not able to notify
a rfkill state change if it is down NM cannot recognise when the device can
be brought up again.
Dan, is that correct?
Regards,
Helmut
next prev parent reply other threads:[~2008-12-01 21:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 12:11 iwlwifi - rfkill only works if the interface is up Helmut Schaa
2008-12-01 13:08 ` Tomas Winkler
2008-12-01 15:04 ` Helmut Schaa
2008-12-01 17:43 ` Tomas Winkler
2009-01-05 14:43 ` Helmut Schaa
2008-12-01 15:30 ` Marcel Holtmann
2008-12-01 15:34 ` Helmut Schaa
2008-12-01 15:59 ` Marcel Holtmann
2008-12-01 16:16 ` Helmut Schaa
2008-12-01 21:12 ` John W. Linville
2008-12-01 21:50 ` Helmut Schaa [this message]
2008-12-03 22:48 ` Dan Williams
2008-12-02 12:59 ` Henrique de Moraes Holschuh
2008-12-02 13:14 ` Marcel Holtmann
2008-12-02 15:03 ` Henrique de Moraes Holschuh
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=200812012250.37587.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=dcbw@redhat.com \
--cc=holtmann@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).