linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Werner Almesberger <werner@openmoko.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rfkill: how murderous can it be ?
Date: Tue, 13 Jan 2009 00:54:01 +0000	[thread overview]
Message-ID: <20090113005401.GA7565@srcf.ucam.org> (raw)
In-Reply-To: <20090112191514.GA22112@almesberger.net>

On Mon, Jan 12, 2009 at 05:15:14PM -0200, Werner Almesberger wrote:

> Alternatively, we could just power down the whole WLAN module. That is
> easily done and very reliable. However, MAC state (ESSID, keys, and a
> host of other settings) is obliterated if we do this. A watchful user 
> space (e.g., wpa_supplicant) could then restore the status quo ante.

Some platform rfkill methods will perform a logical PCI hotplug of the 
device, without any means of notifying the driver beforehand. Since this 
will destroy the driver structure, I think we really need to leave state 
restoration up to userspace.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2009-01-13  0:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:15 rfkill: how murderous can it be ? Werner Almesberger
2009-01-12 19:31 ` Hans Henry von Tresckow
2009-01-13 13:14   ` Henrique de Moraes Holschuh
2009-01-13 16:11     ` Werner Almesberger
2009-01-13 20:56       ` Henrique de Moraes Holschuh
2009-01-12 19:34 ` Dan Williams
2009-01-12 19:49   ` Michael Buesch
2009-01-12 21:13   ` Werner Almesberger
2009-01-13 15:17     ` Michael Buesch
2009-01-13  0:54 ` Matthew Garrett [this message]
2009-01-13 13:21   ` Henrique de Moraes Holschuh
2009-01-13 13:40     ` Johannes Berg
2009-01-15  2:16       ` 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=20090113005401.GA7565@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=werner@openmoko.org \
    /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).