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-…https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-panda-…
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.08https://launchpad.net/linaro-android/+milestone/11.07https://launchpad.net/linaro-android/+milestone/11.06
for examples.
Welcome to the Panda-LEB PoC role!
-Zach
Status:
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/WeeklyReport
Meeting
Minutes:https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2…
Highlights:
Group is now finishing the plans for 1109. Emphasis will be given on
completing some of the work threads, as well as fixing bugs. The status
report link above has a complete list of the work, including work which
does not finish in 1109 but has items to be done on the way to completion.
Also there is progress in LP: the group has now a project group and all
subprojects will be defined in the coming weeks. This is part of the
transition to monthly blueprints.
Best,
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I did the following cpuset configuration:
if [ ! -d /sys/fs/cgroup ]; then
echo "cgroup not supported by the kernel"
else
mount -t cgroup cgroup /sys/fs/cgroup
# needed to have the cgroup values inherited from
# the parent cgroup
echo 1 > /sys/fs/cgroup/cgroup.clone_children
# create an empty cgroup 'cpu0'
mkdir /sys/fs/cgroup/cpu0
# create an empty cgroup 'cpu1'
mkdir /sys/fs/cgroup/cpu1
# assign cpu number '0' for cgroup cpu0
echo 0 > /sys/fs/cgroup/cpu0/cpuset.cpus
# move outself to this new cgroup
echo $$ > /sys/fs/cgroup/cpu0
# move all the tasks to the cpu0 cgroup
# kernel threads won't be moved, don't worry about the
# the errors.
for i in $(cat /sys/fs/cgroup/tasks); do
echo $i > /sys/fs/cgroup/cpu0/tasks || echo "failed to
add pid $i/$(cat /proc/$i/comm)"
done
# assign a cpu for cgroup cpu1
echo 1 > /sys/fs/cgroup/cpu1/cpuset.cpus
# make cpu1 exclusive so processes belonging
# to the other cgroups won't be able to use it.
echo 1 > /sys/fs/cgroup/cpu1/cpuset.cpu_exclusive
fi
At this point, most of the processes have been moved to the 'cpu0'
cgroup and will use the cpu0 only. That does not prevent the cpu1 to be
used by the kernel threads. Any application launched will run on cpu0 only.
After running 10 infinite loops, the cpu accounting gives:
cat /sys/fs/cgroup/cpu0/cpuacct.usage_percpu
418943579549 0
cat /sys/fs/cgroup/cpu1/cpuacct.usage_percpu
0 0
But the system is:
cat /sys/fs/cgroup/cpuacct.usage_percpu
456741213041 30734572583
My guess is that reflects the kernel booted with the two cpus before we
created the cgroup. I am investigation the 'isolcpus' kernel parameter.
I think it is a good starting point to do some consumption measurements.
Mike, Vincent, what do you think ? Do you need more informations or
anything else ?
Thanks
-- Daniel
- --
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOU6AVAAoJEAKBbMCpUGYAbQoH/0NeKLecIuMT57B/w1Jid/bn
yzqD3zwMt0EfUwfsU6H5dAYgumMzKmWWXR9+7FvYhkcckXfzumiMLFKhIybrUSz/
LW7ymHwxXcHWqBTKwMCasHzo9WhlRTlLA1pGAqo0qtG1IBpalE68ZRwItdY/HSOw
0mDGoegq4DHQtcF64XwGRZJo2wAsamtlWGejFdqLQU4FONyYI42rLXMNAG6VD3vG
CJrIudH5hLz3ZBdHYeRB6kWaj1O4skAW6fgySASiqFWoEaZzvT/7UuVBEYawpuyT
Pm+U9OHAfHUWfnyDASFfx6ZQKRS5Uk40XzThjGgwoo598EN8FXZD3N6UZ1WmL2U=
=H00Z
-----END PGP SIGNATURE-----
Hello,
Initial integration of Android Build and LAVA was launched in 11.07, so
works fore more than month now, but you couldn't pleasantly look at its
results. Thanks to efforts of the Validation team, now much improved UI
integration is launched, see "Test results" section at
https://android-build.linaro.org/builds/~linaro-android/panda/#build=250
for example.
For me, this is important point - there're lot to fix, improve, and
extends yet, but finally it feels like we have advanced, powerful,
extensible testing platform straight in our hands.
Kudos to Validation team!
--
Best Regards,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
---------- Forwarded message ----------
From: Peter Maydell
Date: 30 August 2011 13:07
Subject: request for testing: qemu-linaro git tree
To: linaro-toolchain
Hi; I've just completed a tricky rebase of qemu-linaro on upstream;
there were several invasive upstream changes which have landed
recently and which meant that I had to tweak a lot of the qemu-linaro
patches as I did the rebase. I've tested the results but it's possible
that some breakage may have slipped through...
So if you're a regular user of qemu-linaro's system mode and feel
like checking the sources out of git:
git://git.linaro.org/qemu/qemu-linaro.git
building them and testing that the things you regularly do with it
haven't regressed, then I'd appreciate it, and you can help us avoid
any nasty surprises in the next (2011.09) release.
Thanks!
-- Peter Maydell
Nipuna from TI mentioned that the Linaro Android vs Regular Android
demo is posted at http://www.pandaboard.org/. Hopefully we'll be able
to create an even better demo that shows how awesome the work we do
here is!
-Zach
