public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Langdale <philipl@overt.org>
To: "Robert M. Albrecht" <mail@romal.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug 10173 / Bluetooth on Toshiba & Compal laptops
Date: Mon, 15 Dec 2008 17:35:30 -0500	[thread overview]
Message-ID: <bbd413efc08484efe55c558e9a0980fb@localhost> (raw)
In-Reply-To: <4946BE11.5080501@romal.de>


On Mon, 15 Dec 2008 21:29:05 +0100, "Robert M. Albrecht" <mail@romal.de>
wrote:
> Hi,
> 
> anyone working on toshiba_acpi or omnibook module ?
> 
> toshiba_acpi:
> 
>
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=c41a40c58b623f97dd2e23aa3baab2cedb47d99f
> 
> The rfkill-switch does not work. The device is disabled when switched of,

> but it gets not reenabled. But the bluetooth dongle is enabled after
> booting.
> 
> AFAIK this only works for Toshiba manufactured devices (toshiba_acpi),
not 
> for Compal manufactured.

The officially stated maintainer for toshiba_acpi seems to be out of
contact,
but I'm responsible for the rfkill patch. I can only say that the patch is
designed
to re-enable bluetooth when the hardware kill switch is de-asserted and
that I tested
this to work before the change was merged. If it doesn't work now, it's
either:

a) a regression introduced by one of the fixes for laptops with no
bluetooth device. I
   consider this unlikely.

b) different behaviour in your model of toshiba vs. mine

c) a difference in how you've got the kill switch configured in sysfs. Not
sure if that's
   even possible.

As you might conclude, I suspect B.

--phil

  reply	other threads:[~2008-12-15 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 20:29 Bug 10173 / Bluetooth on Toshiba & Compal laptops Robert M. Albrecht
2008-12-15 22:35 ` Philip Langdale [this message]
2008-12-15 22:34   ` Robert M. Albrecht
2008-12-15 22:47     ` Philip Langdale
2008-12-23  7:04       ` Robert M. Albrecht
2008-12-23  9:06         ` Philip Langdale

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=bbd413efc08484efe55c558e9a0980fb@localhost \
    --to=philipl@overt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@romal.de \
    /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