From: Helmut Schaa <helmut.schaa@googlemail.com>
To: samuel@sortiz.org
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
ipw3945-devel@lists.sourceforge.net, mabbaswireless@gmail.com,
tomas.winkler@intel.com, yi.zhu@intel.com,
reinette.chatre@intel.com, dcbw@redhat.com
Subject: Re: [PATCH] iwl3945: report killswitch changes even if the interface is down
Date: Wed, 14 Jan 2009 19:39:42 +0100 [thread overview]
Message-ID: <200901141939.43292.helmut.schaa@gmail.com> (raw)
In-Reply-To: <4db8d83d05d00146e1b2ad0921dbaedd@localhost>
Am Mittwoch, 14. Januar 2009 schrieb samuel@sortiz.org:
>
> Hi Helmut,
>
> On Wed, 14 Jan 2009 16:58:50 +0100, Helmut Schaa
> <helmut.schaa@googlemail.com> wrote:
> > Currently iwl3945 is not able to report hw-killswitch events while the
> > interface is down. This has implications on user space tools (like
> > NetworkManager) relying on rfkill notifications to bring the interface
> > up once the wireless gets enabled through a hw killswitch.
> >
> > Thus enable the device already in iwl3945_pci_probe instead of iwl3945_up
> > and poll the CSR_GP_CNTRL register to update the killswitch state every
> > two seconds. The polling is only needed on 3945 hardware as this adapter
> > does not use interrupts to signal rfkill changes to the driver (in case
> no
> > firmware is loaded). The firmware loading is still done in iwl3945_up.
> The patch looks good and makes sense.
> However, it would be nice to cancel the rfkill polling work once the
> firmware is loaded, as we'll then get card state notifications.
Right, missed that somehow. I'll prepare a second version tomorrow.
Thanks,
Helmut
prev parent reply other threads:[~2009-01-14 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:58 [PATCH] iwl3945: report killswitch changes even if the interface is down Helmut Schaa
2009-01-14 17:46 ` samuel
2009-01-14 18:39 ` Helmut Schaa [this message]
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=200901141939.43292.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=dcbw@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mabbaswireless@gmail.com \
--cc=reinette.chatre@intel.com \
--cc=samuel@sortiz.org \
--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).