[Bug 4840] New: Bluetooth broken on h4000
bugzilla-daemon at amethyst.openembedded.net
bugzilla-daemon at amethyst.openembedded.net
Sat Nov 15 18:52:13 UTC 2008
http://bugs.openembedded.net/show_bug.cgi?id=4840
Summary: Bluetooth broken on h4000
Classification: Unclassified
Product: Openembedded
Version: Angstrom unstable
Platform: ARM
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: org.openembedded.dev
AssignedTo: openembedded-issues at lists.openembedded.org
ReportedBy: bluelightning at bluelightning.org
Using a self-built image from .dev on my h4150 (2.6.21-hh20 kernel), bluetooth
seems not to be working. At first I could not get anything but "Initialisation
timed out" but then I figured out I had to load the h4000_bt module. Problem
#1.
Problem #2 came when I tried hciattach again:
---------------------------------
root at h4000:~# hciattach /dev/ttyS1 texas 115200
Found a Texas Instruments chip!
Firmware file : /lib/firmware/TIInit_2.3.16.bts
can't open firmware file: No such file or directory
Warning: cannot find BTS file: /lib/firmware/TIInit_2.3.16.bts
Can't set device: Protocol not supported
Can't initialize device: Protocol not supported
---------------------------------
The hciattach process then freezes (can't be killed even with -9).
I found a firmware file matching that filename
(http://forum.xda-developers.com/attachment.php?attachmentid=24294&d=1125443135),
and put it in /lib/firmware. The blue LED came on for a very short time this
time (after "Loaded BTS script" below) but then went off:
---------------------------------
root at h4000:~# hciattach /dev/ttyS1 texas 115200
Found a Texas Instruments chip!
Firmware file : /lib/firmware/TIInit_2.3.16.bts
Loaded BTS script version 1
Can't set device: Protocol not supported
Can't initialize device: Protocol not supported
---------------------------------
Then hciattach froze as above.
--
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Openembedded-issues
mailing list