linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by Milo Casagrande

Hello everyone, the Infrastructure team is going to perform a small update of Android Build frontend today at 12UTC. The deployment shouldn't take more than 10 minutes. Only the frontend will be affected. If the downtime will cause you significant problems, please get in touch with us. Thanks. -- Milo Casagrande Infrastructure Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

12 years, 11 months

[PATCH 0/3] Fixing build error with android-3.7

by Tushar Behera

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

12 years, 11 months

[PATCH] bootwrapper: Enable non-secure access to the CCI

by Jon Medhurst (Tixy)

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

12 years, 11 months

[PATCH] bootwrapper: Fix check for architected timer

by Jon Medhurst (Tixy)

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

12 years, 11 months

New WiFi access points in LAVA

by Dave Pigott

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

12 years, 11 months

[PATCH 1/2 v2] ab8500: Remove initial "UNKNOWN" battery-type string assignment

by Rajanikanth H.V

From: "Rajanikanth H.V" <rajanikanth.hv(a)stericsson.com> DT property 'stericsson,battery-type' shall be one of supported technology type Acked-by: Lee Jones <lee.jones(a)linaro.org> Signed-off-by: Rajanikanth H.V <rajanikanth.hv(a)stericsson.com> --- drivers/power/ab8500_bmdata.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/drivers/power/ab8500_bmdata.c b/drivers/power/ab8500_bmdata.c index 03cc528..2230b2c 100644 --- a/drivers/power/ab8500_bmdata.c +++ b/drivers/power/ab8500_bmdata.c @@ -461,7 +461,6 @@ bmdevs_of_probe(struct device *dev, struct device_node *np_bat_supply; struct abx500_bm_data *bat; const char *btech; - char bat_tech[8]; int i, thermistor; *battery = &ab8500_bm_data; @@ -488,12 +487,10 @@ bmdevs_of_probe(struct device *dev, "stericsson,battery-type", NULL); if (!btech) { dev_warn(dev, "missing property battery-name/type\n"); - strcpy(bat_tech, "UNKNOWN"); - } else { - strcpy(bat_tech, btech); + of_node_put(np_bat_supply); + return -EINVAL; } - - if (strncmp(bat_tech, "LION", 4) == 0) { + if (strncmp(btech, "LION", 4) == 0) { bat->no_maintenance = true; bat->chg_unknown_bat = true; bat->bat_type[BATTERY_UNKNOWN].charge_full_design = 2600; @@ -508,7 +505,7 @@ bmdevs_of_probe(struct device *dev, if (thermistor == NTC_EXTERNAL) { btype->batres_tbl = temp_to_batres_tbl_ext_thermistor; - } else if (strncmp(bat_tech, "LION", 4) == 0) { + } else if (strncmp(btech, "LION", 4) == 0) { btype->batres_tbl = temp_to_batres_tbl_9100; } else { -- 1.7.10.4

12 years, 11 months

[RFC v2 PATCH 0/2] sched: Integrating Per-entity-load-tracking with the core scheduler

by Preeti U Murthy

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

12 years, 11 months

[PATCH] ab8500: remove explicit handling of battery type

by Rajanikanth H.V

From: "Rajanikanth H.V" <rajanikanth.hv(a)stericsson.com> property, battery-type shall be one of supported technology type instead blank - refer: Documentation/devicetree/bindings/power_supply/ab8500/fg.txt for the list supported types - this patch appends to ab8500 bm devs DT binding patch set ref: commit-id e0f1abeba5c2d8a2183566717d99294fd1a29c2e git://git.infradead.org/battery-2.6.git - promote ab8500_fg probe to happen before ab8500_btemp probe as btemp driver depends on fuelgauge list, ref: ab8500_fg_get(...) Signed-off-by: Rajanikanth H.V <rajanikanth.hv(a)stericsson.com> --- drivers/power/Makefile | 2 +- drivers/power/ab8500_bmdata.c | 10 +++------- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/power/Makefile b/drivers/power/Makefile index 696e3a9..070c73d 100644 --- a/drivers/power/Makefile +++ b/drivers/power/Makefile @@ -38,7 +38,7 @@ obj-$(CONFIG_CHARGER_PCF50633) += pcf50633-charger.o obj-$(CONFIG_BATTERY_JZ4740) += jz4740-battery.o obj-$(CONFIG_BATTERY_INTEL_MID) += intel_mid_battery.o obj-$(CONFIG_BATTERY_RX51) += rx51_battery.o -obj-$(CONFIG_AB8500_BM) += ab8500_bmdata.o ab8500_charger.o ab8500_btemp.o ab8500_fg.o abx500_chargalg.o +obj-$(CONFIG_AB8500_BM) += ab8500_bmdata.o ab8500_charger.o ab8500_fg.o ab8500_btemp.o abx500_chargalg.o obj-$(CONFIG_CHARGER_ISP1704) += isp1704_charger.o obj-$(CONFIG_CHARGER_MAX8903) += max8903_charger.o obj-$(CONFIG_CHARGER_TWL4030) += twl4030_charger.o diff --git a/drivers/power/ab8500_bmdata.c b/drivers/power/ab8500_bmdata.c index 03cc528..f16b60c 100644 --- a/drivers/power/ab8500_bmdata.c +++ b/drivers/power/ab8500_bmdata.c @@ -461,7 +461,6 @@ bmdevs_of_probe(struct device *dev, struct device_node *np_bat_supply; struct abx500_bm_data *bat; const char *btech; - char bat_tech[8]; int i, thermistor; *battery = &ab8500_bm_data; @@ -488,12 +487,9 @@ bmdevs_of_probe(struct device *dev, "stericsson,battery-type", NULL); if (!btech) { dev_warn(dev, "missing property battery-name/type\n"); - strcpy(bat_tech, "UNKNOWN"); - } else { - strcpy(bat_tech, btech); + return -EINVAL; } - - if (strncmp(bat_tech, "LION", 4) == 0) { + if (strncmp(btech, "LION", 4) == 0) { bat->no_maintenance = true; bat->chg_unknown_bat = true; bat->bat_type[BATTERY_UNKNOWN].charge_full_design = 2600; @@ -508,7 +504,7 @@ bmdevs_of_probe(struct device *dev, if (thermistor == NTC_EXTERNAL) { btype->batres_tbl = temp_to_batres_tbl_ext_thermistor; - } else if (strncmp(bat_tech, "LION", 4) == 0) { + } else if (strncmp(btech, "LION", 4) == 0) { btype->batres_tbl = temp_to_batres_tbl_9100; } else { -- 1.7.10.4

12 years, 11 months

Build publishing guidelines

by Danilo Šegan

Hi all, I want to remind everyone that we are trying to switch to new BUILD-INFO support for restricting/allowing access to all the builds we create and that end up on snapshots.linaro.org (and we want all builds to end up there). BUILD-INFO.txt supports several ways to control access to your files, and ideally, it should be produced along with the build itself: * open: anyone can access * license protected: anyone can access files after they agree to an included license * openid-protection: choose which Launchpad teams someone has to be a member of before they can access any builds (this replaces Apache-based openid protection that we still have for old builds) Short examples for all three are on https://wiki.linaro.org/Platform/Infrastructure/Publishing I am sure you can figure out a lot from these examples, but if you are struggling with anything, Platform Infrastructure team will be glad to help. Look for anyone listed in the topic of #linaro-infrastructure channel. Cheers, Danilo

12 years, 11 months

Test Result Summary for Linaro 12.11 Release (Calendar Week 48)

by Botao Sun

Linaro 12.11 Release (Calendar Week 48): Here is test result summary for Linaro ubuntu image on following boards: 1) ARM Versatile Express A9; 2) Open Embedded SDK; 3) Open Embedded LAMP; 4) Open Embedded Minimum. Synopsis: Audio works on ARM Versatile Express A9 Jelly Bean; DS-5 Data Streaming Doesn't work on ARM Versatile Express A9 ubuntu but works well on Android platform; PHP test passed with issue on Open Embedded LAMP image. 1. ARM Versatile Express A9 + ubuntu (Column AK): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… Latest version of DS-5 (v5.12 build 1571) doesn't work on data streaming, all the other features remain the same. Device Tree is still unavailable due to the defect in UEFI and 480p video playback doesn't work either. For HTML5 YouTube video, after streaming buffer finished, the performance is acceptable. 2. ARM Versatile Express A9 + Android Jelly Bean (Column Q): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… Audio works, now the sound can be heard in Angry Birds and Music App. For latest DS-5 (v5.12 build 1571), data streaming works well. All other features remain the same. 3. Open Embedded SDK in Fast Model (Column C): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… All test cases passed. 4. Open Embedded LAMP in Fast Model (Column C): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… PHP test passed with issue - kernel exception messages observed. However, this issue won't affect the system and other functions. All rest tests passed. 5. Open Embedded Minimum in Fast Model (Column C): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdDhwR… All test cases passed. For the previous week (Calendar week 46) summary, please refer to attachment. Thank you. Best Regards Botao Sun

12 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev