I guess I jumped the gun by backporting the .35 version. It built and seemed to work, but kp'd when pairing, specifically when creating the bluetooth sysfs stuff as it didn't agree with .35. This is an unbackport to .32 for this file, but still required changes, mostly changing hdev->type to hdev->bus to agree with the rest of the .35 backport. Using this file I was able to pair to my mac and transfer a file successfully.
note that debugging lines (marked printk("Fattire: something") or printk("FT") may be in a couple files to help track down where it's kping at the end of the pairing process. I have to go but this is for dalingrin to take over for the moment.. the problem seems to be related to hci_conn_add_sysfs(conn); in net/bluetooth/hci_event.c The reference isntallation I'm using is at: http://www.omapzoom.com/?p=kernel/omap.git;a=tree;hb=p-android-omap-2.6.35 Look there to see how things "should" work.
Still experiencing a kp, but I don't think it's related. Checking this in for others (dalin) to try.
This should work, athough it's only been lightly tested. * Use with bts firmware from TI in /system/etc/firmware * Uses latest gb uim-sysfs * Also includes changes to defconfig, including ext4 support * brings the dead to life btwilink.c is the driver, making a guest appearance from .35.