[Debian-eeepc-devel] Bluetooth: how it won't mess older models

[Iván Sánchez Ortega]

Hi all,


I was able to do a bit of research into the innards of the eeepc acpi module. 
It looks like, when the module is loaded, it queries the BIOS for 
capabilities.

If you run "dmesg | grep -i eee" you'll see something like this:

[   13.468662] Asus EeePC Hotkey Driver
[   13.472634] [eeepc hotk] Hotkey init flags 0x41.
[   13.481527] [eeepc hotk] Get control methods supported: 0x101713


The control methods is actually a bitmap of things that the BIOS is able to 
do. The source code for the eeepc acpi module (either 2.6.25's eeepc-acpi or 
2.6.26's eeepc-laptop) contains the meaning of that "control methods 
supported" bitmap. For example, the last "3" (0011) in the output of my 901 
means "firewire: no, irda: no, bluetooth: yes, wlan: yes").

The module actually checks this bitmap before creating any control files. So, 
models with no BT won't have the BT control file in /proc (or /sys).


However, I'd like to confirm this. Could some owners of 701s and 900s publish 
the following data? (reply here, and/or publish in the wiki, section about 
models)
- Output of "dmesg | grep eee"
- Model number (output of "cat /sys/class/dmi/id/product_name")
- Just in case, BIOS version (output of "cat /sys/class/dmi/id/bios_version")



Thanks,
-- 
----------------------------------
Iván Sánchez Ortega <ivan at sanchezortega.es>

"Uno de los grandes misterios de la vida ¿cómo puedes hacer arder un coche a 
puñaladas y no con una bola de fuego?"
                                                     --Eje
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/attachments/20080903/dace8615/attachment.pgp