Red Hat Bugzilla – Bug 437091
RFE: include toshbt in the kernel
Last modified: 2013-01-10 02:02:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20080201 Firefox/22.214.171.124
Description of problem:
I found a module which allows me to use the internel bluetooth adaptor in my laptop. This would be nice to have in the kernel.
Maybe it just needs to be added to the toshiba_acpi kernel module.
This works for me on my Toshiba Qosmio G30-163 laptop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. insmod toshiba_acpi and the toshbt module.
Bluetooth usb devices was powered on and attached. The regular bluetooth framework took over and it works.
Created attachment 297751 [details]
Module source in case the site goes away.
Adding FutureFeature keyword to RFE's.
I'm not enthusiastic about this as-is. It duplicates a lot of the toshiba_acpi
code and provides a custom interface in /proc. I'd prefer to merge this into
toshiba_acpi and add an rfkill interface to make it easier to deal with.
The code for activating the bluetooth radio is now merged in 2.6.28-rc1.
The relevant commit is:
but there are probably a couple more you want to pickup anyway.
Can we apply a patch to the Fedora kernel until we rebase on 2.6.28?
Otherwise we will continue to have broken support for these laptops for quite some time..
Commited to rawhide CVS
Hi Matthew, thanks a lot for your quick reaction.
I just checked the patch in cvs and I think it's possible you pulled an incomplete patch as it seems missing the Kconfig added flags.
To be sure, you probably want to use the plain version of the diff:
Sorry for the hassle
The Kconfig dependencies are always selected in our kernel, so it's more cosmetic than anything else.
OK. I hope it will appear in a F10 kernel soon...
Shipped in F10 and is also in F11 rawhide.
Yeah. I just need to note bluetooth works as expected only with a full boot. After a suspend/resume cycle it is not reactivated.
I'd need to check if 2.6.29 fixes the issue...