The last 2 things to do are to fix the build system so that when you build concurrently the modules get into the system.tar.bz2.
Things should get installed to:
out/target/product/pandaboard/system/modules
...and they do when you build without -j
The file:
device/linaro/common/tasks/kernel.mk
Contains the recipe to build the modules and copy them over. The problem is that the kernel may get built before or after the system.tar.bz2 gets produced. The system.tar.bz2 gets built via a recipe:
core/Makefile:786:system_tar := $(PRODUCT_OUT)/system.tar core/Makefile:787:INSTALLED_SYSTEMTARBALL_TARGET := $(system_tar).$(SYSTEM_TARBALL_FORMAT) core/Makefile:788:$(INSTALLED_SYSTEMTARBALL_TARGET): PRIVATE_SYSTEM_TAR := $(system_tar) core/Makefile-789-$(INSTALLED_SYSTEMTARBALL_TARGET): $(FS_GET_STATS) $(INTERNAL_SYSTEMIMAGE_FILES) core/Makefile-790- $(build-systemtarball-target) core/Makefile-791- core/Makefile-792-.PHONY: systemtarball-nodeps core/Makefile-793-systemtarball-nodeps: $(FS_GET_STATS) \ core/Makefile-794- $(filter-out systemtarball-nodeps stnod,$(MAKECMDGOALS)) core/Makefile-795- $(build-systemtarball-target)
I had tried a few things, but I think if:
core/Makefile-793-systemtarball-nodeps: $(FS_GET_STATS) \ core/Makefile-794- $(filter-out systemtarball-nodeps stnod,$(MAKECMDGOALS))
...is updated to depend on a kernel module rule, possibly broken out from device/linaro/common/tasks/kernel.mk things will probably work okay.
Once this is done the insmod commands that are already a part of:
out/target/product/pandaboard/root/init.omap4430.rc
namely:
insmod /system/modules/st_drv.ko insmod /system/modules/bluetooth.ko insmod /system/modules/bnep.ko insmod /system/modules/hci_uart.ko insmod /system/modules/rfcomm.ko insmod /system/modules/btwilink.ko
insmod /system/modules/wl12xx.ko insmod /system/modules/wl12xx_sdio.ko
will work against the already being installed binaries at:
out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl128x-fw-ap.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl1271-fw.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl128x-fw.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl1271-nvs.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl1271-fw-2.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl1271-nvs-example-wl128x.bin out/target/product/pandaboard/system/lib/firmware/ti-connectivity/wl1271-fw-ap.bin
and
ls out/target/product/pandaboard/system/lib/firmware ti-connectivity TIInit_7.2.31.bts
which does get installed correctly.
The second part is to get the BT daemon pulled into Android. Dave this may be a good job for you to get up to speed on Android.
The BPs are here:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-panda-w... https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-panda-b...
Vishal, please update these.
FYI BPs are all filed on a monthly basis. Each BP should track the production of tangible result every month. If a BP isn't finished and there's nothing tangible to show for it, it gets moved (like these) to the next month. If there is something tangible, then it gets split.
Each BP has 3 required sections:
Headline: Something punchy about what this BP is going to produce like, "Panda-LEB is now shipping with a 3.0 kernel"
Acceptance: What's considered done.
Work items: A list of items with TODO, INPROGRESS and DONE.
You can also put a notes section together
Notes:
Feel free to look through:
https://launchpad.net/linaro-android/+milestone/11.08 https://launchpad.net/linaro-android/+milestone/11.07 https://launchpad.net/linaro-android/+milestone/11.06
for examples.
Welcome to the Panda-LEB PoC role!
-Zach