Greetings! I'm responsible for getting my company's Bluetooth application up and running on the Android platform, and the HTC Dream in particular. One of our requirements was support for Bluetooth L2CAP enhanced retransmission and streaming modes. I've implemented the necessary changes to the L2CAP core on a Debian system running 2.6.29 and 2.6.30-rc* kernels. (The patchset has been submitted to the linux-bluetooth mailing list, a GSOC student is currently integrating and extending it's functionality.)
I'm now faced with the prospect of getting it running on the HTC Dream, running Android 1.5, which uses kernel 2.6.27. I've successfully compiled the android-msm-2.6.29 kernel from the Android kernel tree with the L2CAP patches applied. Unfortunately, when running this kernel, the prebuilt TI wireless module will not load, due to it being compiled against a different kernel version. # insmod wlan.ko > insmod: init_module 'wlan.ko' failed (Exec format error) > #dmesg > <3>[ 1634.844741] wlan: version magic '2.6.27-00205-gf2dabc0 preempt > mod_unload ARMv6 ' should be '2.6.29-00362-gba9bd6e preempt mod_unload ARMv6 > ' > Getting both Bluetooth eL2CAP and Wireless/WiFi working concurrently is critical to our application. Previous messages on this list imply 2.6.29 will be the next supported Android kernel. Does this mean that the TI module has been compiled against this kernel version? If so, is it available? If not, would my only recourse be backporting the changes to 2.6.27? But if I do so, won't backporting to 2.6.27 and applying my patches still result in a different git commit hash in the version magic string? Or does it only check the kernel version numbers? --nathan --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
