Return-Path: <linux-kernel-owner+w=401wt.eu-S1753867AbYKBJXx@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753867AbYKBJXx (ORCPT <rfc822;w@1wt.eu>);
	Sun, 2 Nov 2008 04:23:53 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753207AbYKBJXn
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sun, 2 Nov 2008 04:23:43 -0500
Received: from cavan.codon.org.uk ([93.93.128.6]:39039 "EHLO
	vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753163AbYKBJXl (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sun, 2 Nov 2008 04:23:41 -0500
Date: Sun, 2 Nov 2008 09:23:36 +0000
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
Message-ID: <20081102092336.GD10983@srcf.ucam.org>
References: <20081031110502.18e33eba@doriath.conectiva> <490B0D75.8020601@tuffmail.co.uk> <20081031142318.GA9009@srcf.ucam.org> <40f31dec0810311135w76c01729lef1a6c93f18c0095@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40f31dec0810311135w76c01729lef1a6c93f18c0095@mail.gmail.com>
User-Agent: Mutt/1.5.12-2006-07-14
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: mjg59@codon.org.uk
X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 945
Lines: 20

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/