Hello Michael. I believe that Keith Conger supplied you with the 3.18 backport drivers for Bluetooth, right? I have Keith's patches sitting in my review queue, but I haven't yet created a branch with them. The problem that I'm running into is that the 3.8 kernel has the capemgr in it, but the later kernels do not. So, Bluetooth drivers in the newer kernels aren't readily available for BBBAndroid without a lot of screwing around. The drivers that you need are available in the 3.14 kernel, but the 3.14 kernel does not have support for dynamic loading of device tree overlays in it. Only 3.8 has this feature, which is why I am sticking with 3.8 for BBBAndroid. I want to make it easy for people to try different hardware configurations and easily prototype Android interfacing code, though some features requiring the drivers from newer kernels (like Bluetooth drivers) aren't available because of this.
You could try just dropping the 3.14 kernel into the BBBAndroid build process as you are doing, but you must make sure that the device tree (.dtb) in the boot partition matches the kernel. The FTDI serial output will tell you of any issues with the bootloader and help you diagnose these sorts of problems. If all of the lights are on, you are having a problem very early in the boot process. My guess is that it is a mismatch of some sort among the bootloader, uEnv.txt file, the device tree .dtb, and the kernel. You probably haven't gotten far enough along in the build process to worry about having the correct kernel modules installed in the root file system, but that shouldn't be a problem if you are using my makefile. My makefile installs the modules into place for you. Also, make sure that you have the Android staging drivers (binder, anonymous shared memory, low memory killer, etc.) enabled in you kernel configuration for the 3.14 kernel. You were asked about all of those options when you built the kernel because you were using a kernel configuration file for the 3.8 kernel with your 3.14 kernel. There are a number of mismatches in the options between the two kernels, so the kernel Kconfig system was asking you to sort out the differences. Andrew On Wednesday, March 11, 2015 at 3:00:40 PM UTC-4, [email protected] wrote: > > Hi Andrew, > > Thanks for the great job you've doing on the beagleboard. > For the project I'm currently working on I included bluetooth support to > the build. However, it seems that the le functionality isn't working > because it relies on some modules not available in the 3.8 kernel. > > Some people pointed out the I should upgrade to kernel 3.14. However, I'm > kind of I'm the dark here and I don't really know what I'm doing wrong. > > Would it be possible to point me in the right direction? > > Currently I modidified the repo manifest to fetch the beaglebone 3.14 > kernel and replace it with the original bbbkernel in the manifest. I ran > the make oldconfig on the kernel to merge the 3.4 config with the new 3.14 > config. However, after running the build I tried to boot it on the BBB and > it failed to boot. The 4 userleds seem to stay lit. > > After doing the make oldconfig I had to enter a lot of new options. I'm > not really sure what I was doing there... > > Cheers, > Michael > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
