public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: corentincj@iksaif.net, Woody Suwalski <woodys@xandros.com>,
	Sitsofe Wheeler <sits@sucs.org>,
	acpi4asus-user@lists.sourceforge.net,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: Is rfkill class really appropriate for eeepc-laptop?
Date: Fri, 26 Sep 2008 15:14:48 +0100	[thread overview]
Message-ID: <48DCEE58.5060004@tuffmail.co.uk> (raw)
In-Reply-To: <20080926135517.GA6273@srcf.ucam.org>

Matthew Garrett wrote:
> On Fri, Sep 26, 2008 at 02:49:53PM +0100, Alan Jenkins wrote:
>
>   
>> I was wrong to say that rfkill support was already in mainline.  But it
>> is introduced by Matthew's patch "eeepc-laptop: Use standard
>> interfaces", as posted and reviewed on the linux-acpi list.  I think
>> this is a bad idea.  Surely the whole point of rfkill is to let
>> NetworkManager do power management *without* having to do different
>> things for different laptops?
>>     
>
> No, it's to use allow the OS to control whatever mechanism the platform 
> provides for making the radio stop transmitting. The fact that this is, 
> uh, "interestingly" implemented on the Eee doesn't alter that.

So rfkill should be allowed to mean "entire PCI device goes away,
network interface will vanish" - just so long as it comes back correctly
when re-enabled :-).

>  We should just sort out the hotplug code...
>   

Ok.  I have a little knowledge, I'll see if I can be dangerous.  My real
question was, is it safe to merge your rfkill support before this is
sorted out?

Thanks
Alan

  reply	other threads:[~2008-09-26 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080918133144.GA4338@silver.sucs.org>
     [not found] ` <48D564A8.7030009@xandros.com>
     [not found]   ` <20080921102246.GA27071@silver.sucs.org>
     [not found]     ` <48D660C5.6070204@xandros.com>
     [not found]       ` <48D69052.1040908@tuffmail.co.uk>
     [not found]         ` <48D6AC5E.70502@xandros.com>
2008-09-26 13:49           ` Is rfkill class really appropriate for eeepc-laptop? Alan Jenkins
2008-09-26 13:55             ` Matthew Garrett
2008-09-26 14:14               ` Alan Jenkins [this message]
2008-09-26 14:17                 ` Matthew Garrett
2008-09-26 16:48               ` 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=48DCEE58.5060004@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentincj@iksaif.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=sits@sucs.org \
    --cc=woodys@xandros.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