From: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ak@linux.intel.com, Len Brown <lenb@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] ACPI: compal-laptop: use rfkill switch subsystem
Date: Thu, 3 Jul 2008 06:48:18 +0200 [thread overview]
Message-ID: <20080703064818.35ee2532@debian> (raw)
In-Reply-To: <20080703021433.GC20410@khazad-dum.debian.net>
Dnia 2008-07-02, o godz. 23:14:33
Henrique de Moraes Holschuh <hmh@hmh.eng.br> napisał(a):
[...]
> That doesn't look like a new-style (i.e. what is in net-next-2.6) rfkill
> support. Could you take a look on the new (and I sure hope, vastly
> improved) Documentation/rfkill.txt in net-next-2.6, and switch the driver to
> RFKILL_STATE_UNBLOCKED, RFKILL_STATE_SOFT_BLOCKED, etc? After a quick look,
> it looks like Compal won't need RFKILL_STATE_HARD_BLOCKED (thinkpad-acpi
> does, because some thinkpads have a master wireless kill switch), but
> still...
Compal has hardware wireless kill switch (without software it kill all radios
rf and disconnecting bluetooth from usb bus). Does he should generate
SW_RFKILL_ALL or something like this?
--
Cezary Jackiewicz
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-03 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 19:45 [PATCH 1/1] ACPI: compal-laptop: use rfkill switch subsystem Cezary Jackiewicz
2008-07-03 0:17 ` Matthew Garrett
2008-07-03 2:14 ` Henrique de Moraes Holschuh
2008-07-03 4:48 ` Cezary Jackiewicz [this message]
2008-07-03 12:52 ` Henrique de Moraes Holschuh
2008-07-03 5:05 ` Cezary Jackiewicz
2008-07-03 12:54 ` 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=20080703064818.35ee2532@debian \
--to=cezary.jackiewicz@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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.