Ticket #553 (closed defect: fixed)
gta01-pm-bt.ko is missing from modules
| Reported by: | bmidgley@… | Owned by: | laforge@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | kernel | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: | buglog@…, bluelightning@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
As documented in the wiki on http://wiki.openmoko.org/wiki/Bluetooth_Support
there is a module gta01-pm-bt that is required before the bluetooth adapter can
be used. It is not being built into the ramdisk.
I'm using a kernel and image dated 1 May 2007:
openmoko-devel-image-fic-gta01-20070501054014.rootfs.jffs2
uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin
Change History
comment:2 Changed 6 years ago by laforge@…
- Status changed from new to assigned
this is not a module, but built into the kernel. however, due to a mismatch of
platform devices and corresponding drivers, I believe the driver was not bound
to the actual device.
comment:3 Changed 6 years ago by bmidgley@…
I probably should have mentioned this is a P1 device.
I look forward to doing some bluetooth hacking when you have a fix ready :)
comment:4 Changed 6 years ago by bmidgley@…
even after
modprobe hci_usb
and
echo 1>/sys/bus/platform/devices/gta01-pm-bt.0/power_on
the bluetooth adapter does not appear using hciconfig -a
I've tried this on the latest dev image and on an image I built using
mokomakefile. Same result.
comment:5 Changed 6 years ago by laforge@…
What hardware revision do you have? "P1 device" doesn't really make too much
sense, since P1 still has not started yet.
comment:6 Changed 6 years ago by bmidgley@…
ok sorry I just assumed it was a p1 since it arrived very recently...
hardware gta01
revision 0240
comment:8 Changed 6 years ago by bmidgley@…
for what it's worth, I have been able to get the bluetooth radio to work using a
recently built image. It shows up in lsusb and hciconfig.
I load hci_usb automatically and then manually power up the radio twice in a row
and then reset it. Even that doesn't always succeed, but at least with some luck
I can get the radio working and do some testing.
I suspect it's a fluke with this p0 phone.

sorry, I meant root filesystem above not ramdisk.