Summary: | Linux 2.6.27 bug in eeepc-laptop no bluetooth in /sys/devices/platform/eeepc/ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lxg <mail2lx> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
lxg
2008-11-11 14:21:03 UTC
What is the effect of this bug? I can't imagine that bluetooth doesn't work just because this file isn't present? Bluetooth does work. I can scan, pair, etc. just fine. But /sys/devices/platform/eeepc/* allow to activate/deactivate the devices by echoing 0/1 to them. I wouldn't know what other file in the /sys subsystem would allow to do the same for bluetooth. In my specific case, this feature is needed by the eee-control[1] tool, which uses the /sys/devices/platform/eeepc/* files. (The eee-control tool is not in Portage, but I maintain an ebuild and intend to propose it for Portage inclusion, as soon as it runs smooth on Gentoo.) [1] http://www.zirona.com/misc/code/eee-control/ This is not a kernel bug, this is just a feature that isn't implemented in the kernel yet. Any userspace tool should be able to handle that "error" condition OK, unless it specifically requires the Ubuntu kernel. I would suggest that you email Adam McDaniel and ask him if he will submit the patches upstream. I checked, and they are not queued for either the 2.6.28 or 2.6.29 upstream releases at this time. He may be reluctant to send them on - the website says that the bluetooth interface doesn't always work. Once these patches do get sent upstream, please reopen this bug and we will consider adding them to gentoo-sources. Daniel, thank you very much for taking your time and looking into this issue. I think I will have to find another solution for this. |