From: Fabien Crespel <fabien@crespel.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 04/13] rfkill: add parameter to disable radios by default
Date: Tue, 24 Jun 2008 22:29:25 +0200 [thread overview]
Message-ID: <48615925.8010203@crespel.net> (raw)
In-Reply-To: <1214330213.23127.9.camel@localhost.localdomain>
Dan Williams wrote :
> On Tue, 2008-06-24 at 19:06 +0200, Fabien Crespel wrote:
>
>> Indeed, I think it would be better to let the driver choose the default state
>> (initialization) instead of forcing it when registering. This would allow drivers
>> to restore the device state after a reboot or shutdown (provided the firmware
>> stores it, which is the case at least on my ASUS F3JC laptop).
>>
>
> Do you mean your laptop BIOS stores the value in nvram somewhere? What
> specific driver reads that value back out?
>
> Dan
>
Yes, the laptop BIOS stores the value. Reading it back is done the same
way as reading the WLAN/BT status later (through an ACPI method), so the
driver only has to read and write the status at initialization to
restore the device status & LEDs (because the reported status doesn't
reflect the hardware status at boot time).
- Fabien.
next prev parent reply other threads:[~2008-06-24 20:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 20:22 [GIT PATCH] rfkill rework for 2.6.27 (v3) Henrique de Moraes Holschuh
2008-06-23 20:22 ` [PATCH 01/13] rfkill: clarify meaning of rfkill states Henrique de Moraes Holschuh
2008-06-23 20:22 ` [PATCH 02/13] rfkill: fix minor typo in kernel doc Henrique de Moraes Holschuh
2008-06-23 20:22 ` [PATCH 03/13] rfkill: handle SW_RFKILL_ALL events Henrique de Moraes Holschuh
2008-06-23 20:22 ` [PATCH 04/13] rfkill: add parameter to disable radios by default Henrique de Moraes Holschuh
2008-06-24 14:05 ` Dmitry Baryshkov
2008-06-24 17:06 ` Fabien Crespel
2008-06-24 17:56 ` Dan Williams
2008-06-24 20:29 ` Fabien Crespel [this message]
2008-06-24 21:49 ` Dan Williams
2008-06-25 7:23 ` Fabien Crespel
2008-06-24 23:17 ` Henrique de Moraes Holschuh
2008-06-25 8:11 ` Fabien Crespel
2008-06-25 14:02 ` Henrique de Moraes Holschuh
2008-06-24 17:07 ` Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 05/13] rfkill: add read-write rfkill switch support Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 06/13] rfkill: add the WWAN radio type Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 07/13] rfkill: rework suspend and resume handlers Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 08/13] rfkill: add notifier chains support Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 09/13] rfkill: add type string helper Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 10/13] rfkill: add uevent notifications Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 11/13] rfkill: drop current_state from tasks in rfkill-input Henrique de Moraes Holschuh
2008-06-23 20:49 ` Ivo van Doorn
2008-06-23 20:23 ` [PATCH 12/13] rfkill: do not allow userspace to override ALL RADIOS OFF Henrique de Moraes Holschuh
2008-06-23 20:23 ` [PATCH 13/13] rfkill: document rw rfkill switches and clarify input subsystem interactions Henrique de Moraes Holschuh
2008-06-26 13:13 ` [GIT PATCH] rfkill rework for 2.6.27 (v3) Dmitry Baryshkov
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=48615925.8010203@crespel.net \
--to=fabien@crespel.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.