Hi all,
As part of our investigations into the Linux scheduler we've
interacted with Juri Lelli at the University of Pisa (cc'ed) who is
part of a group that is working on a DEADLINE scheduler[1] for
Linux[2].
While we're coming at this from a power managment angle[3], I suspect
that LEG and LNG already have real-world usecases that would benefit
from deadline scheduler found in other RTOSes.
So I think it makes sense to merge Juri's tree into linux-linaro going
forward to allow easier experimentation. Does LEG and LNG have any
interest in this at this point?
Juri has expressed an interest in maintaining a current branch of the
code that could be merged into our monthly release. In return, real
world usecases will improve his chances of getting the code merged
into mainline.
Regards,
Amit
[1] http://retis.sssup.it/?q=node/35
[2] https://lkml.org/lkml/2013/2/11/373
[3] Mostly involving discussions at this point, no real engineering
effort invested yet
Calendar Week 21, 2013: Here is test result summary for Linux Linaro ubuntu
Raring image on following boards:
1) ARM Versatile Express A9;
2) Samsung Arndale;
3) TI Panda 4430;
4) TI Panda 4460;
5) ST Ericsson Snowball.
Synopsis: STE Snowball is not stable enough; "Reboot" works well on ARM
Versatile Express A9.
1. ARM Versatile Express A9 + Linux Linaro Raring (Column W):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Only "Halt" test failed, all other features work well.
2. Samsung Arndale + Linux Linaro Raring (Column Q):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS…
"Halt" test failed; some errors show in power management test. All other
features work well.
3. TI Panda 4430 + Linux Linaro Raring (Column W):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
WiFi and display output are unavailable; some errors show in power
management test. All other features work well.
4. TI Panda 4460 + Linux Linaro Raring (Column W):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
WiFi and display output are unavailable; Kernel panic happened in power
management test. All other features work well.
5. ST Ericsson Snowball + Linux Linaro Raring (Column X):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFJ4X…
System is not stable enough. Sometimes booting failed, and "apt-get" failed
as well. Many CRC errors got observed in SD MMC test, display output is
unavailable. "Reboot" test failed.
For the release critical test summary of last week (Calendar Week 20),
please refer to attachment.
Thank you.
Best Regards
Botao Sun
hi
When i download the
git.linaro.org/git-ro/landing-teams/working/arm/kernel.git, there are
branches relates to gator.
I set up the enviroment at TC2 with gator and Dstream. I want to show
the CPU frequencies of big and little clusters, so i add code in gator
to get the frequency of the clusters. But it seems that gator wakes
up in period and send out the message. So is there any way that make
gator to wake up based on events of cpu frequency changing, and send
out the message to Dstream?
Hi,
There is a build failure for STE Snowball on "linux-arm-soc-for-next"
branch in Linaro Kernel CI system:
https://ci.linaro.org/jenkins/job/linux-arm-soc-for-next/hwpack=snowball,la…
which is caused by:
01:31:32
/mnt/ci_build/workspace/linux-arm-soc-for-next/hwpack/snowball/label/kernel_cloud/drivers/mfd/ab8500-debugfs.c:95:23:
fatal error: mach/irqs.h: No such file or directory
01:31:32 #include <mach/irqs.h>
01:31:32 ^
01:31:32 compilation terminated.
01:31:32 make[3]: *** [drivers/mfd/ab8500-debugfs.o] Error 1
01:31:32 make[2]: *** [drivers/mfd] Error 2
01:31:32 make[1]: *** [drivers] Error 2
To solve this issue, here is the patch which Linux Walleij provided on 11
April 2013:
https://lkml.org/lkml/2013/4/11/101
Would anyone like to merge the patch to fix this compiling error?
Thank you in advance for your efforts!
Best Regards
Botao Sun
Hi Marcin,
I notice you've created a number of shell scripts to manage checking out
multiple git repositories, specific revisions of git repositories for a
release, etc. Repo [1] does this stuff pretty well that you might want to
consider as an eventual alternative.
1. https://gerrit.googlesource.com/git-repo/+/stable
Here's one example of a Repo manifest for an OpenEmbedded-based project,
albeit with extra packages thrown in. You can ignore the things with a path
outside of oe-core.
https://www.codeaurora.org/gitweb/quic/le/?p=mdm/manifest.git;a=blob;f=caf_…
Once you've got a git repository the with manifest file, the usage mechanics
are something along the lines of downloading repo itself if not already
available [2], passing the manifest repository's URL (can be local) to repo
init, and then running repo sync to clone all the repositories from the source
URLs to the destination paths at the revisions specified in the manifest file.
2. http://source.android.com/source/downloading.html
Regards,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
Hi all,
Foundation model is closed source propertiary software, but i want to know how i can get more detailed and comprehensive technical support?
I want to know the work procedure of boot wrapper. For example, make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf.
What use are the arguments of BOOTARGS and FDT_SRC? Whether they are used by foundation model or real OS ? what real use is vexpress-foundation-v8.dts?
Thanks
Xiaoke Wu
Hi all,
I just wanted to forward this thread from LAKML to linaro-dev:
http://article.gmane.org/gmane.linux.ports.tegra/10683
Seems there is lots desire for an improvement to automated build
coverage and automated reporting along with it.
Regards,
Mike
Hello Everyone,
I am reposting the following message to linaro-dev as I am using the
following linaro toolchain for ARM64 cross-compilation:
https://wiki.linaro.org/HowTo/BuildArm64Kernel
In fact, I am trying to compile qemu for Aarch64 but so far I haven't been able to configure qemu for this purpose.
My first objective is to just configure and cross-compile qemu for Aarch64, which is currently blocked by the qemu's dependency on
cross-compiled "glib-2.12" or later.
For example, when I use the following configure command:
./configure --cross-prefix=aarch64-linux-gnu- --target-list=arm-softmmu --enable-fdt --static
I get the following error:
ERROR: glib-2.12 required to compile QEMU
This is a well-known dependency and the following pages are linked to this issue (directly or indirectly) and I have tried all of them without any success:
https://bugs.launchpad.net/linaro-oe/+bug/1097561http://people.debian.org/~wookey/bootstrap.htmlhttp://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompil…https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/arm64bootstrap
I have also tried the latest git repository from John Rigby but I get the same error:
https://git.linaro.org/gitweb?p=people/jcrigby/qemu-aarch64.git;a=summary
Anyways, I want to know how we can resolve this dependency ?
Some of you might suggest to cross-compile the glib-2.12 from sources found at:
http://www.linuxfromscratch.org/blfs/view/6.3/general/glib2.htmlhttp://www.gtk.org/api/2.6/glib/glib-cross-compiling.html
but even this option doesn't work for me as the apparent lacking support for Aarch64 in "glib-2.12".
I have used the following configure command:
./configure --prefix=/my/prefix/path --host=aarch64-linux-gnu --cache-file=aarch64.cache
with the following aarch64.cache file contents:
glib_cv_long_long_format=I64
glib_cv_stack_grows=no
Any pointers and/or directions for a possible solution will be highly appreciated.
Thanks in advance,
Hamayun
Various SoCs with arm processors define their own platform hotplug related
functions. These functions can be defined as part of the core cpu hotplug
functions, this will avoid the duplication. This patchset is intended to
address this issue.
This patchset covers arm-Cortex-A9 of exynos, imx, realview, spear and
vexpress SoCs. Not having h/w, the patch is not tested.
Sanjay Singh Rawat (6):
ARM: cpuhotplug: move common hotplug related functions to core
ARM: imx: use the core cpu hotplug functions
ARM: RealView: use the core cpu hotplug functions
ARM: spear: use the core cpu hotplug functions
ARM: vexpress: use the core cpu hotplug functions
ARM: EXYNOS: use the core cpu hotplug functions
arch/arm/include/asm/hotplug.h | 24 ++++++++++++++
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/cpuhotplug.c | 64 ++++++++++++++++++++++++++++++++++++++
arch/arm/mach-exynos/hotplug.c | 40 ++----------------------
arch/arm/mach-imx/hotplug.c | 22 +------------
arch/arm/mach-realview/hotplug.c | 37 +---------------------
arch/arm/mach-spear/hotplug.c | 37 +---------------------
arch/arm/mach-vexpress/hotplug.c | 38 +---------------------
8 files changed, 95 insertions(+), 168 deletions(-)
create mode 100644 arch/arm/include/asm/hotplug.h
create mode 100644 arch/arm/kernel/cpuhotplug.c
--
1.7.9.5
