Hey
If you try latest daily hwpacks + latest linaro-image-tools (0.4.4 or
bzr) you should be getting Device Tree aware images for boards which
support it (mostly i.MX51 and OMAP ATM).
Feedback and bug reports welcome!
Cheers,
--
Loïc Minier
Hi Linaro folks,
I'd like to set up an automated testing environment to help me maintain
the MMC subsystem: just a few boards of different architectures booting
each day's linux-next and running basic performance and integrity tests
without any manual intervention involved. I've got access to remote
power switches, so I think it'll be pretty easy to get running.
I was thinking that this will probably find generic kernel bugs as they
appear in linux-next, and was wondering whether Linaro has any interest
in such testing -- if so, do you have any preferred software to use for
it, or any resources I should take a look at to avoid duplicating work?
I've been looking at using autotest, but it seems a bit abandoned
lately.
Would be grateful for any pointers or ideas. Thanks!
- Chris.
--
Chris Ball <cjb(a)laptop.org> <http://printf.net/>
One Laptop Per Child
Enclosed you'll find a link to the agenda, minutes and actions from the
Linaro Toolchain working group weekly meetings of April 18 & 21, 2011.
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-18https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-21
== Summary ==
* Released Linaro GCC 4.5 and 4.6 2011.04
* Released Linaro GDB 7.2 2011.04
* Linaro QEMU 2011.04 is almost out the door
* Blueprints from this cycle have been checked and the status updated
* A draft of the session topics has been done
* Engineers are now fleshing out the topics into draft blueprints
* SMS has been backported to Linaro 4.5
Regards,
Mounir
Enclosed you'll find a link to the agenda, minutes, actions and IRC logs
from the
Linaro kernel working group weekly meetings of April 18, 2011.
https://wiki.linaro.org/WorkingGroups/Kernel/Meetings/2011-04-18
== Summary ==
* Went over the cycle 11.11 Technical Requirements ownership and estimates
* Deepak Saxena has agreed to join us. He will be taking over as Kernel WG
lead.
* Tixy will handle K5.1 TR kprobes
* John estimate to do full conversion of kconfig will take 6 PM's since
that involves lots of folks, and possibly reworking major bits of the
kconfig language.
* Thomas would like to help with k8.1, Memory Regions Support
Hello list,
Today we're announcing a new technical preview of ARM optimized
toolchain for Android platform by Linaro[1].
Linaro is a NFP (Not For Profit) organization that aims to make
embedded open source development easier and faster. Regardless of
Android release cycle from AOSP, Linaro would like to bring the latest
and ARM optimizing open source technologies to the common software
foundation for software stack, and Linaro toolchain[2] deals with all
aspects of system-level tools - the core development toolchain
(compiler, assembler, linker, debugger).
In this announcement, the technical preview of ARM optimized toolchain
for Android is available for evaluation: (source repository and binary
package)
https://wiki.linaro.org/Platform/Android/Toolchain
An early activity of the Android Platform Team has been to run the
Android benchmark suite to show the gains possible in going from the
default Google 4.4 based toolchain to the Linaro 4.5 toolchain. The
experimental benchmarks were run on a 600 MHz Cortex-A8 board running
Android 2.2: (unofficial, for reference only)
https://wiki.linaro.org/JimHuang/Sandbox/LinaroToolchainAndroidBenchmarking
Developers can utilize the optimization techniques from GNU Toolchain
and Linaro's ARM improvements through Linaro Toolchain for Android and
NDK. For example, skia benchmark[3] brings 11% performance
improvements after using Linaro Toolchain.
Linaro's Android platform team plans to deliver the final linaro-11.05
release, and you can check out the status of open development:
https://launchpad.net/linaro-android/
On-going Blueprints:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-toolch…https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-toolch…https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-google…
Sincerely,
Jim Huang,
Android platform team,
Linaro
[1] http://www.linaro.org/
[2] https://wiki.linaro.org/WorkingGroups/ToolChain
[3] Linaro uses the same toolchain benchmark as Google compiler team
does: https://wiki.linaro.org/Platform/Android/UpstreamToolchain
The question of the size impact of building the kernel in Thumb-2 came
up to day, so I extracted some quick numbers:
$ size vmlinux-*
text data bss dec hex filename
8420507 463356 826928 9710791 942cc7 vmlinux-arm
6715539 463260 826928 8005727 7a285f vmlinux-thumb2
This is for a recent mainline kernel built with the linaro omap config.
In this case we save about 20% for code and read-only data (i.e.,
text) and 17.5% overall -- which accounts for a little under 2MB saved
in this example.
This doesn't take loadable modules into accout; we can probably expect
to see a similar size ratio there.
Cheers
---Dave
Mounting system as mmc@blk0p2 did not work. Replaced it with
/dev/block/mmcbkk0p2 as a temporary solution.
---
init.rc | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/init.rc b/init.rc
index c2836b9..e5b64ed 100644
--- a/init.rc
+++ b/init.rc
@@ -91,10 +91,9 @@ loglevel 3
on fs
# mount mmc partitions
- mount ext4 mmc@blk0p2 /system
- mount ext4 mmc@blk0p2 /system ro remount
- mount ext4 mmc@blk0p3 /cache
- mount ext4 mmc@blk0p5 /data
+ mount ext4 /dev/block/mmcblk0p2 /system ro
+ mount ext4 /dev/block/mmcblk0p3 /cache
+ mount ext4 /dev/block/mmcblk0p5 /data
on post-fs
# once everything is setup, no need to modify /
--
1.7.1