From: "John W. Linville" <linville@tuxdriver.com>
To: mohamed salim abbas <mabbaswireless@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
linux-wireless@vger.kernel.org, tomas.winkler@intel.com,
yi.zhu@intel.com, reinette.chatre@intel.com
Subject: Re: [RFC][RFT] fix iwlagn hw-rfkill while the interface is down
Date: Wed, 17 Dec 2008 15:29:43 -0500 [thread overview]
Message-ID: <20081217202943.GB3516@tuxdriver.com> (raw)
In-Reply-To: <b3153e950812171210n7247bevc9470fa47942ce92@mail.gmail.com>
On Wed, Dec 17, 2008 at 12:10:11PM -0800, mohamed salim abbas wrote:
> the interrupt moved from pci_probe to mac_start for power saving. once
> the interface is up the driver will read some register to know rfkill
> status, if the interface in down the driver don't care to keep track
> of rfkill switch. I wonder what the purpose of changing this behavior?
I think it still isn't settled in everyone's minds whether rfkill
only matters if the device is "up" or if it is something that
e.g. NetworkManager might want to monitor as a clue to bring the
device up or down in response to rfkill changes.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-12-17 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 12:07 [RFC][RFT] fix iwlagn hw-rfkill while the interface is down Helmut Schaa
2008-12-17 20:10 ` mohamed salim abbas
2008-12-17 20:29 ` John W. Linville [this message]
2008-12-17 21:31 ` Dan Williams
2009-01-05 14:56 ` Helmut Schaa
2009-01-06 15:59 ` Dan Williams
2009-01-06 16:41 ` Marcel Holtmann
2009-01-06 16:49 ` Dan Williams
2009-01-06 17:05 ` Marcel Holtmann
2009-01-06 18:54 ` Dan Williams
2009-01-06 19:39 ` Marcel Holtmann
2009-01-06 19:41 ` Helmut Schaa
2008-12-18 12:54 ` Helmut Schaa
2008-12-18 12:19 ` Helmut Schaa
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=20081217202943.GB3516@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@gmail.com \
--cc=reinette.chatre@intel.com \
--cc=tomas.winkler@intel.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).