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 for
While we're coming at this from a power managment angle, 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
 Mostly involving discussions at this point, no real engineering
effort invested yet
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?
There is a build failure for STE Snowball on "linux-arm-soc-for-next"
branch in Linaro Kernel CI system:
which is caused by:
fatal error: mach/irqs.h: No such file or directory
01:31:32 #include <mach/irqs.h>
01:31:32 compilation terminated.
01:31:32 make: *** [drivers/mfd/ab8500-debugfs.o] Error 1
01:31:32 make: *** [drivers/mfd] Error 2
01:31:32 make: *** [drivers] Error 2
To solve this issue, here is the patch which Linux Walleij provided on 11
Would anyone like to merge the patch to fix this compiling error?
Thank you in advance for your efforts!
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  does this stuff pretty well that you might want to
consider as an eventual alternative.
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.
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 , 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.
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
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?
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