Date: Fri, 29 Aug 2008 14:12:16 -0700
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)
Message-Id: <20080829141216.f0d69ae4.akpm@linux-foundation.org> (sfid-20080829_231401_330820_B3F3331A)
In-Reply-To: <47479.65.113.40.1.1219443825.squirrel@overt.org>
References: <47479.65.113.40.1.1219443825.squirrel@overt.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-wireless-owner@vger.kernel.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.