Hi,
I managed to start bluetooth on nookie froyo, BT scan is working well(on command line), sometimes it shows devices in the android gui.
The steps : ( use at your own risk and only for comfirmed devs)
Add bluetooth capabilities (HCILL) in kernel
Toggle the WL12XX_RFKILL flag on in evt1a defconfig.
Take the bluetooth firmware (bts file) from gforge.ti ( wl1271 firmware) for froyo pandroid and put it into /system/lib/firmware, alias /lib/firmware to /system/lib/firmware (useful for command line).
boot the kernel
and then
echo 0 >/sys/class/rfkill/rfkill0/state
echo 1 >/sys/class/rfkill/rfkill0/state
hciattach -s 115200/dev/ttyS1 texas
hcitool scan must show you your BT devices (if discoverable)
Stability is not yet here, Maybe some problems with UART high speed handling ?
This is very positive, it seems that the wl1271 chip is well connected to omap3621...
I will continue to dig ...
Occip
I managed to start bluetooth on nookie froyo, BT scan is working well(on command line), sometimes it shows devices in the android gui.
The steps : ( use at your own risk and only for comfirmed devs)
Add bluetooth capabilities (HCILL) in kernel
Toggle the WL12XX_RFKILL flag on in evt1a defconfig.
Take the bluetooth firmware (bts file) from gforge.ti ( wl1271 firmware) for froyo pandroid and put it into /system/lib/firmware, alias /lib/firmware to /system/lib/firmware (useful for command line).
boot the kernel
and then
echo 0 >/sys/class/rfkill/rfkill0/state
echo 1 >/sys/class/rfkill/rfkill0/state
hciattach -s 115200/dev/ttyS1 texas
hcitool scan must show you your BT devices (if discoverable)
Stability is not yet here, Maybe some problems with UART high speed handling ?
This is very positive, it seems that the wl1271 chip is well connected to omap3621...
I will continue to dig ...
Occip
Last edited by a moderator: