From: Andrew Morton <akpm@linux-foundation.org>
To: philipl@overt.org
Cc: linux-kernel@vger.kernel.org, mjg59@srcf.ucam.org,
toshiba_acpi@memebeam.org, ivdoorn@gmail.com,
linux-wireless@vger.kernel.org, hmh@hmh.eng.br
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v7)
Date: Fri, 29 Aug 2008 14:12:16 -0700 [thread overview]
Message-ID: <20080829141216.f0d69ae4.akpm@linux-foundation.org> (raw)
In-Reply-To: <47479.65.113.40.1.1219443825.squirrel@overt.org>
On Fri, 22 Aug 2008 18:23:45 -0400 (EDT)
philipl@overt.org wrote:
> There's been a patch floating around for toshiba_acpi that exports an ad-hoc
> /proc interface to toggle the bluetooth adapter in a large number of Toshiba
> laptops. I'm not sure if it's still relevant for the latest models, but it is
> still required for older models such as my Tecra M3.
>
> This change pulls in the low level Toshiba-specific code from the old patch and
> sets up an rfkill device and a polled input device to track the state of the
> hardware kill-switch.
ERROR: "rfkill_force_state" [drivers/acpi/toshiba_acpi.ko] undefined!
ERROR: "rfkill_free" [drivers/acpi/toshiba_acpi.ko] undefined!
ERROR: "rfkill_register" [drivers/acpi/toshiba_acpi.ko] undefined!
ERROR: "rfkill_allocate" [drivers/acpi/toshiba_acpi.ko] undefined!
ERROR: "rfkill_unregister" [drivers/acpi/toshiba_acpi.ko] undefined!
I'll stick a `select RFKILL' in there, but it'll probably blow up
in other ways. select usually does.
next prev parent reply other threads:[~2008-08-29 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 22:23 [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v7) philipl
2008-08-29 21:12 ` Andrew Morton [this message]
2008-08-29 21:26 ` [PATCH 1/1] toshiba_acpi: Add support for bluetooth togglingthrough " Philip Langdale
2008-08-29 21:32 ` 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=20080829141216.f0d69ae4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=philipl@overt.org \
--cc=toshiba_acpi@memebeam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox