The bootwrapper is really doubling as firmware, so it doesn't make
sense for it to drop out of the Secure World before getting a
chance to parse its parameters and configuration.
Instead, it should make sense to delay switching to the Normal
World for as long as possible so that we have a chance to do any
required firmware-level configuration in the Secure World first.
This quick hack is ***completely untested***, since I'm not working
with any suitable kernel tree right now.
If someone with a KVM tree ready to run could give it a try,
that would definitely save me some time.
Review also welcome (naturally)
Changes since v1:
* Don't rely on preservation of lr or sp across enter_hyp (this
doesn't work because those registers are banked per-mode).
I'm still not convinced this series works, due image/model/dtb
mismatches in my testing, but execution at least reaches the kernel
now.
Cheers
---Dave
Dave Martin (3):
bootwrapper: Fix misaligned Hyp mode vector table
bootwrapper: Refactor entry into Hyp mode to be more reusable
bootwrapper: Delay switch to Hyp mode until kernel entry
boot.S | 58 +++++++++++++++++++++++++++++++++++++-------------------
semi_loader.h | 6 +++-
2 files changed, 42 insertions(+), 22 deletions(-)
--
1.7.4.1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Dave Martin (3):
bootwrapper: Fix misaligned Hyp mode vector table
bootwrapper: Refactor entry into Hyp mode to be more reusable
bootwrapper: Delay switch to Hyp mode until kernel entry
boot.S | 58 +++++++++++++++++++++++++++++++++++++-------------------
semi_loader.h | 6 +++-
2 files changed, 42 insertions(+), 22 deletions(-)
--
1.7.4.1
Hi there
I'm looking for the correct RT patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) for a Linaro Linux source. Just for a start I tried with linux-linaro-3.4-2012.05-1 with the RT patch patch-3.4-rc2-rt1.patch.bz2 and got some build errors due to undeclared methods/variables. I would like to ask which of these two (linaro-linux and RT patch) goes together ?
ps. I checked out question http://ask.linaro.org/questions/336/do-real-time-patches-work-on-ubuntu-bui… and am wondering if that describes it or what ?
Regards
Einar M. Bjorgvinsson
Embedded Software Engineer
Marel ehf.
Iceland
Currently we don't support migration of currently running timers. Current code
flow in __mod_timer() is:
- Find a cpu where we should migrate the timer
- Check if timer is currently running
- If yes, don't migrate.
In this process, the first step is a unnecessary activiy, if the timer is
currently running. This patch tries to avoid it in such cases.
Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org>
---
kernel/timer.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/kernel/timer.c b/kernel/timer.c
index 8c5e7b9..6e5bf98 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -755,23 +755,23 @@ __mod_timer(struct timer_list *timer, unsigned long expires,
debug_activate(timer, expires);
- cpu = smp_processor_id();
+ /*
+ * Should we try to migrate timer?
+ * However we can't change timer's base while it is running, otherwise
+ * del_timer_sync() can't detect that the timer's handler yet has not
+ * finished. This also guarantees that the timer is serialized wrt
+ * itself.
+ */
+ if (likely(base->running_timer != timer)) {
+ cpu = smp_processor_id();
#if defined(CONFIG_NO_HZ) && defined(CONFIG_SMP)
- if (!pinned && get_sysctl_timer_migration() && idle_cpu(cpu))
- cpu = get_nohz_timer_target();
+ if (!pinned && get_sysctl_timer_migration() && idle_cpu(cpu))
+ cpu = get_nohz_timer_target();
#endif
- new_base = per_cpu(tvec_bases, cpu);
+ new_base = per_cpu(tvec_bases, cpu);
- if (base != new_base) {
- /*
- * We are trying to schedule the timer on the local CPU.
- * However we can't change timer's base while it is running,
- * otherwise del_timer_sync() can't detect that the timer's
- * handler yet has not finished. This also guarantees that
- * the timer is serialized wrt itself.
- */
- if (likely(base->running_timer != timer)) {
+ if (base != new_base) {
/* See the comment in lock_timer_base() */
timer_set_base(timer, NULL);
spin_unlock(&base->lock);
--
1.7.12.rc2.18.g61b472e
For people trying to build Linaro Android 12.08 there's an issue with an
unknown reference in powertop2.0.
Here's what to do:
cd android
edit .repo/manifest.xml
Find:
<project groups="path:external/powertop,name:tools/powertop-2.0"
name="tools/powertop-2.0" path="exter\
nal/powertop" remote="linaro-other"
revision="c80f55d9d1b823b7f6ff447eefc8a6ba04b939c4"/>
...and remove the line. Then
cp .repo/manifest.xml ../
cd ..
rm -rf android/
edit linaro_android_build_cmds.sh
and change
curl -k
http://snapshots.linaro.org/android/~linaro-android/vexpress-jb-gcc47-armlt…
>
.repo/manifest.xml
to
cp ../manifest.xml .repo/
and rerun linaro_android_build_cmds.sh
You can also take a tip build which is not susceptible to this problem. Tip
builds that have been booted are listed at:
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AnpUtxWjZbP9dGg0d…
If you still get errors after this, then its a general git timeout error.
Just delete the android/ directory and start again or cd android/; repo
./sync
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
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
This patchset adds support for AArch64 in all required classes:
- insane
- kernel-arch
- siteinfo
Everything is from public available information (binutils, linux).
Calendar Week 39: Here is test result summary for Linaro ubuntu 12.09
Release on following boards:
1) ARM Versatile Express A9;
2) Samsung Origen;
3) TI Panda Board 4430;
4) TI Panda Board 4460.
*Synopsis: "DEADLOCK" error has disappeared during boot process, except on
TI Panda platform, although it won't affect system running. Both 480p &
1080p videos can be played on Panda board with an extra package installed -
"ubuntu-omap4-extras-multimedia". Device Tree feature is still unavailable
on vexpress A9. WiFi, Bluetooth and video playback are unavailable on
Samsung Origen.*
1. vexpress A9 + ubuntu (Column AB):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Device Tree blob files have recovered, although this feature is still
unavailable due to a UEFI defect, which Ryan is working on that. 480p video
playback still doesn't work on this release image. YouTube HTML5 video now
can be played, although the frame rate is low, which is as expected. All
other features remain the same as last week.
2. Origen + ubuntu (Column W):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEowN…
"DEADLOCK" error has gone on this image, and kernel version has been
upgraded to 3.6.0-1. All other features remain the same as last week.
3. Panda 4430 + ubuntu (Column Y):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
YouTube HTML5 video now can be played well, but due to Audio over HDMI
failure, no sound can be heard. Although file transfer via Bluetooth is
still unavailable, Bluetooth headset works well. 480p video on SD card can
be played well if package "ubuntu-omap4-extras-multimedia" be installed in
advance. 1080p video can be played with a low frame rate. All power
management test has passed (or skipped properly) on this image. No
significant change on all the other features.
4. Panda 4460 + ubuntu (Column X):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Bluetooth headset doesn't work here, it hangs the board during the pair
process. Hardware acceleration works well. 3.5mm Audio input is still
unavailable and suspend / resume test failed as well. No change on all the
other features compare with last week test.
For the previous week (Calendar week 38) summary, please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Hi there,
Is there any sensible comparison document for gcc vs rvct in terms of speed, code size, feature set? Is there any reason / use case to recommend rvct over gcc for non-Linux s/w?
Thx
nicolas
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 12.654.784