Following patches are required on android-3.7 branch for the androidized
kernel for Origen to build.
Needs testing on USB gadget functionalities.
Tushar Behera (3):
usb: gadget: android: Fix build error because of removal of
usb_gadget_controller_number
usb: gadget: android: Fix build error because of change in composite
driver framework
netfilter: xt_quota2: Remove extra parameter from
netlink_kernel_create
drivers/usb/gadget/android.c | 18 +++++-------------
drivers/usb/gadget/composite.c | 5 ++++-
net/netfilter/xt_quota2.c | 5 +++--
3 files changed, 12 insertions(+), 16 deletions(-)
--
1.7.4.1
We boot the kernel in non-secure mode and by default access to
the CCI device is not enabled for non-secure access, so we must
enable this if we want Linux to manage CPU hotplug on big.LITTLE
models.
Signed-off-by: Jon Medhurst <tixy(a)linaro.org>
---
semi_loader.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/semi_loader.c b/semi_loader.c
index f8be94d..f9d36e5 100644
--- a/semi_loader.c
+++ b/semi_loader.c
@@ -263,6 +263,8 @@ static void init_cci(unsigned cci)
/* Wait while change pending bit of status register is set */
while(io32(cci+0xc) & 0x1)
{}
+
+ io32(cci+0x8) = 1; /* Enable non-secure access to CCI */
}
static void configure_from_fdt(struct loader_info *info)
--
1.7.10.4
From: Will Deacon <will.deacon(a)arm.com>
We need to set the flags when checking the feature register.
Signed-off-by: Will Deacon <will.deacon(a)arm.com>
---
I found this patch in another fork of the bootwrapper and it looks like
something we should have. On the A15 and big.LITTLE setups I've tested
it makes no difference so I guess the z flag was already clear or the
architected timers are already running at 24MHz.
boot.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/boot.S b/boot.S
index 40ebd33..dd453e3 100644
--- a/boot.S
+++ b/boot.S
@@ -78,7 +78,7 @@ start:
@
mrc p15, 0, r0, c0, c1, 1 @ CPUID_EXT_PFR1
lsr r0, r0, #16
- and r0, r0, #1 @ Check generic timer support
+ ands r0, r0, #1 @ Check generic timer support
beq 1f
ldr r0, =24000000 @ 24MHz timer frequency
mcr p15, 0, r0, c14, c0, 0 @ CNTFRQ
--
1.7.10.4
Hi all,
I've now added 3 routers supporting b, g and n. They are:
LAVA-WiFi-B
Fixed IP address: 192.168.1.17
SSID: LAVA-WiFi-B ChangeHuntDevise
LAVA-WiFi-G
Fixed IP address: 192.168.1.24
SSID: LAVA-WiFi-G DoubleSuezBun
LAVA-WiFi-N
Fixed IP address: 192.168.1.9
SSID: LAVA-Wife-N GeneralWaveFlight
Thanks
Dave
This approach aims to retain the current behavior of load balancer with the
change being only in the metric consumed during load balancing,
without unnecessary introduction of new variables.This RFC has been posted to
evaluate its design;to see if this is the right way to go about introducing
per-entity-load-tracking metric for the consumers of the same; in this
specific case,the load balancer.Once the design has been approved off,I can
go around to testing it.
The patch has been based out of tip-master:HEAD at commit 8a1d31c703d
Subject:Merge branch 'x86/urgent'
Grateful to Peter Zijlstra and Ingo Molnar for their valuable feedback on v1
of the RFC which was the foundation for this version.
PATCH[1/2] Aims at enabling usage of Per-Entity-Load-Tracking for load balacing
PATCH[2/2] The crux of the patchset lies here.
---
Preeti U Murthy (2):
sched: Revert temporary FAIR_GROUP_SCHED dependency for load-tracking
sched: Use Per-Entity-Load-Tracking metric for load balancing
include/linux/sched.h | 9 +-----
kernel/sched/core.c | 19 +++++-------
kernel/sched/fair.c | 76 +++++++++++++++++++++----------------------------
kernel/sched/sched.h | 9 +-----
4 files changed, 43 insertions(+), 70 deletions(-)
--
Preeti U Murthy