From: Matthew Garrett <mjg@redhat.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
"Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
willy@linux.intel.com, lrodriguez@atheros.com
Subject: Re: ath5k gets lost with eeepc-laptop removal
Date: Sun, 2 Nov 2008 09:23:36 +0000 [thread overview]
Message-ID: <20081102092336.GD10983@srcf.ucam.org> (raw)
In-Reply-To: <40f31dec0810311135w76c01729lef1a6c93f18c0095@mail.gmail.com>
On Fri, Oct 31, 2008 at 08:35:47PM +0200, Nick Kossifidis wrote:
> It doesn't leave the radio in a state that's not transmitting, it
> leaves the card in a state that doesn't get any power at all. I don't
> see any reason for this, how do you define "safe" ?
The rfkill core has no concept of what the underlying hardware
implementation is. The fact that you can see the card at all is a bug
triggered by the fact that we don't currently support PCIe hotplug on
this type of machine (I've just sent a patch that adds a workaround for
that), but the inherent reason for it happening this way is because Asus
implemented it that way in their platform.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-11-02 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 13:05 ath5k gets lost with eeepc-laptop removal Luiz Fernando N. Capitulino
2008-10-31 13:51 ` Alan Jenkins
2008-10-31 14:23 ` Matthew Garrett
2008-10-31 18:35 ` Nick Kossifidis
2008-11-02 9:23 ` Matthew Garrett [this message]
2008-10-31 16:26 ` Nick Kossifidis
2008-10-31 17:19 ` Luiz Fernando N. Capitulino
2008-10-31 18:33 ` Nick Kossifidis
2008-10-31 18:43 ` Luiz Fernando N. Capitulino
2008-10-31 18:48 ` Luiz Fernando N. Capitulino
2008-11-02 9:04 ` Matthew Garrett
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=20081102092336.GD10983@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mickflemm@gmail.com \
--cc=willy@linux.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).