linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Vroon <tony@vroon.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-acpi@vger.kernel.org, ibm-acpi-devel@lists.sourceforge.net
Subject: Re: Bluetooth driver vs RFKILL state LED
Date: Sun, 28 Dec 2008 13:43:03 +0000	[thread overview]
Message-ID: <49578267.6020401@vroon.org> (raw)
In-Reply-To: <200812281224.41223.toralf.foerster@gmx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Toralf Förster wrote:
> I'm wondering why at my ThinkPad T41 the bluetooth LED is on even if I did not 
> compiled bluetooth support into the kernel nor as module.

That LED indicates whether the Bluetooth radio is enabled (powered up,
it is a USB device). Consider it like a light socket. You don't have a
working bulb in there, but you can still switch the socket on & off.
You see the results of your switching the moment you screw in a working
lightbulb (load your Bluetooth driver).

It would in fact be a layering violation to care about whether or not a
Bluetooth driver is loaded when switching the radio on & off. If you
want your Bluetooth to start out off and remain off, you should set your
BIOS up accordingly.

Regards,
Tony V.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklXgmcACgkQp5vW4rUFj5qL8ACeO8mw7Fl5qy5PC0NtqeBkE2Ti
aEEAnRUo1NcZsM3wt9rBW+m/M4UD05Pf
=mNiX
-----END PGP SIGNATURE-----
--
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

      reply	other threads:[~2008-12-28 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-28 11:24 (unknown) Toralf Förster
2008-12-28 13:43 ` Tony Vroon [this message]

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=49578267.6020401@vroon.org \
    --to=tony@vroon.org \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=toralf.foerster@gmx.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;
as well as URLs for NNTP newsgroup(s).