linaro-dev January 2012

linaro-dev@lists.linaro.org

125 participants
124 discussions

by Peter Meerwald

Hello, I've just posted some patches with ARM NEON code to the pulseaudio-discuss mail list (http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-January/01261…) -- this might be of interest to Linaro a stand-alone version of the code is in a Mercurial repo at http://pmeerw.net/hg/pa-neon -- feedback and testing welcome thanks, regards, p. -- Peter Meerwald +43-664-2444418 (mobile)

14 years, 1 month

Linaro Kernel configs (was Re: [RFC PATCH 0/2] thermal: Add generic cpu cooling devices according to thermal framework)

by Amit Kucheria

On Thu, Jan 12, 2012 at 2:33 PM, Lee Jones <lee.jones(a)linaro.org> wrote: > On 12/01/12 12:20, Amit Kucheria wrote: >> On Thu, Jan 12, 2012 at 3:02 AM, Ricardo Salveti >> <ricardo.salveti(a)linaro.org> wrote: >>> On Wed, Jan 11, 2012 at 2:24 AM, Amit Kachhap <amit.kachhap(a)linaro.org> wrote: >>>> Hi Zach/Ricardo, >>>> >>>> All the thermal Kconfigs are enabled in >>>> https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/Kconfig. >>> >>> Great, thanks. >>> >>> Guess we just need to make sure we're in sync with every LT tree >>> (android and package level too). >> >> In the LT-WG call yesterday, Lee wanted us to ping all the LT leads to >> make sure they had these configs enabled in the the kernel. Consider >> this a ping, guys :) >> >> Let us know if you need more information. > > Is this solely an Android thing, or do our Common Linux kernels require > them too? All our work is distro-agnostic. * sched_mc: should get enabled on all kernels since the core feature is now in mainline. * thermal management: should get enabled as we enable various SoCs in the Linaro kernel with SoC-specific drivers

14 years, 1 month

[PATCH v3 0/4] Add SMDK5250 board support

by Chander Kashyap

This patchset add support for Samsung's SMDK5250 board based on EXYNOS5250 based SoC. It also adds support for MMC SPL booting. The porting is done by Samsung engineers at HQ in System LSI Team. I am contributing in upstreaming the code for the board. Based upon discussions following patches are dropped in this version: Exynos: Add CONFIG_EXYNOS4 Macro to EXYNOS4 based boards Exynos: Clock.c: Replace exynos4 prefix with exynos SMDK5250: enable device tree support is squashed with EXYNOS: Add SMDK5250 board support Chander Kashyap (4): Exynos: Clock.c: Use CONFIG_SYS_CLK_FREQ macro ARM: EXYNOS: Add support for Exynos5 based SoCs EXYNOS: Add SMDK5250 board support EXYNOS: SMDK5250: Add MMC SPL support MAINTAINERS | 1 + arch/arm/cpu/armv7/exynos/clock.c | 215 +++++++++- arch/arm/include/asm/arch-exynos/clock.h | 326 ++++++++++++++ arch/arm/include/asm/arch-exynos/cpu.h | 35 ++- arch/arm/include/asm/arch-exynos/gpio.h | 101 ++++- board/samsung/smdk5250/Makefile | 64 +++ board/samsung/smdk5250/lowlevel_init.S | 528 ++++++++++++++++++++++ board/samsung/smdk5250/mem_setup.S | 600 +++++++++++++++++++++++++ board/samsung/smdk5250/mmc_boot.c | 58 +++ board/samsung/smdk5250/smdk5250.c | 125 +++++ board/samsung/smdk5250/smdk5250_setup.h | 589 ++++++++++++++++++++++++ board/samsung/smdk5250/tools/mkexynos_image.c | 117 +++++ boards.cfg | 1 + include/configs/s5pc210_universal.h | 1 + include/configs/smdk5250.h | 188 ++++++++ 15 files changed, 2931 insertions(+), 18 deletions(-) create mode 100644 board/samsung/smdk5250/Makefile create mode 100644 board/samsung/smdk5250/lowlevel_init.S create mode 100644 board/samsung/smdk5250/mem_setup.S create mode 100644 board/samsung/smdk5250/mmc_boot.c create mode 100644 board/samsung/smdk5250/smdk5250.c create mode 100644 board/samsung/smdk5250/smdk5250_setup.h create mode 100644 board/samsung/smdk5250/tools/mkexynos_image.c create mode 100644 include/configs/smdk5250.h -- 1.7.5.4

14 years, 1 month

[ACTIVITY] Android Platform Team 2011-01-04 to 2012-01-10

by Tony Mansson

This information is also available here: https://wiki.linaro.org/Platform/Android/Status/2012-01-12 Key Points for wider discussion =============================== * Ethernet Communication Manager is integrated in ICS * Snowball USB OTG greatly improved. Supports High Speed powered hubs. Team Highlights =============================== * Linaro Android is now based on AOSP version 4.0.3. * The first 12.01 release has been cut. * Wifi is enabled on tracking-panda builds * Progress on Wifi for Snowball. * Good progress on OMX IL for ICS on Origen. * Improvements in binutils. Now at version 2.22.51.0.1 * Improvements in documentation on the wiki. e.g. [[https://wiki.linaro.org/Platform/Android/BuildSource | Building Android Platform Code]] Bugs fixed =============================== * 908956 ICS: Panda: 1080p launcher screen positioning uses 720p origin * 912720 staging-panda build 179 fails to bootup * 878973 Builds can not be compiled with the original AOSP GCC 4.4 toolchain * 890346 Sound doesn't work on panda on ICS * 900508 GLMark2 not available on ICS * 913945 powertop not available on ICS * 894502 No Ethernet Communication Manager on ICS * 908956 ICS: Panda: 1080p launcher screen positioning uses 720p origin * 912229 ffmpeg 0.9.1 is released, linaro-android has 0.9.0 * 867527 All binaries and libraries are mapped rwx on both text and data * 892837 staging-panda and tracking-panda do not come up with the right resolution Miscellaneous =============================== Issues =============================== Blueprints =============================== https://launchpad.net/linaro-android/+milestone/12.01

14 years, 1 month

Monthly Release Thoughts

by Tom Gall

Hi All, I had some thoughts and a suggestion this morning about the monthly release cycle that I'd like to share. Perhaps I'll get booed off the stage, perhaps not. I'm sure it can be improved on. There is a great deal of stress around what blueprints fit into what monthly release boundary. For deliveries like the LEB that combine the fruits of our Linaro labors this makes great sense. Outside of the process for LEB creation and release, I'd like to suggest it's less than efficient and creates a bit of stress as we have the monthly rush to make the release dates. PMs and TLs continually have to be watching for what will and what won't be making dates that fit with the LEB. This passes on the stress to the engineering team, causes some late night hack-a-thons which in turn I believe caused us to rush software what was less than ready to be included in a LEB. I'm sure we all have examples we could point to. To address this I'd like to suggest the following. The production of the LEB and related builds should continue to be on a monthly release cycle. However outside of that process, for the WGs and such, we should go to a process based on continuous integration. As work groups, landing teams and so on, we commit to the LEB process that we have some set of blueprints IN QUEUE, meaning they are being worked on right now. When they go complete if they are LEB bound, they are delivered to the staging overlay. Items in the staging overlay are candidates for promotion to the overlay. When an item in the staging overlay is judged as being ready (bugs are at least triaged and deemed to not be blocking) it is promoted into the overlay from which daily builds are made and the monthly release is made. Packages in the staging overlay are the subject of functional test.IE Does it work? Packages in the overlay are the subject of integration test. IE Does it break the system? Work Groups, Landing Teams will also commit to having a priority list of blueprints and bugs that are being addressed or will be addressed. This keeps the release process and management team aware of what is coming and when. The # of completed work items per week (or other counts) can also help the management team measure forward momentum and progress. In some respects it's subtle process tweek. But I feel shifting part of linaro to a continuous integration / ship when ready model makes sense. In the work groups we are more connected upstream as we stay tune with upstream release boundaries but still want to showcase results in the monthly LEBs. Likewise focus on the LEB continues with higher quality software. It does shift the goal of creating great software by date X, to creating great software and ship when it's ready. Perhaps this would be a good discussion for 1Q12LC. -- Regards, Tom "Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Multimedia Tech Lead | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org w) tom_gall att vnet.ibm.com h) tom_gall att mac.com

14 years, 1 month

Busted my hand may be slow to respond...

by Zach Pfeffer

Off to get a little rest. Good news is they don't think its broken. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

14 years, 1 month

Linaro Connect Q1.12

by Arwen Donaghey

Hi All, You’ll be pleased to see we've now created the e-mail alias for Linaro Connect Q1.12. You can mail connect-q1.12(a)linaro.org for general announcements, and we will also use this alias to advise you of important issues related to and during the event. Everyone who has registered for Linaro Connect Q1.12 is now on this alias. If you’re attending and have not yet registered, please do so asap by clicking this link. ‧ Register for Linaro Connect Q1.12 <http://connect.linaro.org/register-connect/> [1] You’ll also be able to subscribe to sessions at Linaro Connect Q1.12 you are interested in, apply for visas and share travel information with others (may be helpful for sharing taxi rides etc). In addition, please book your accommodation for Linaro Connect Q1.12 before rooms at the hotel run out. As many of you will be staying on for ELC and ABS, we've now updated the accommodation booking link to reflect booking dates from 5th through to 18th February. ‧ Book accommodation for Linaro Connect Q1.12 <http://www.sofitel.com/sofitel/lien_externe.svlt?goto=spec_rate_hotel&sub=I SP&code_hotel=0922&code_chaine=SOF&RA1=lin0502212&RA2=&ragp=0&libelle_tarif= 1&showEco=0&jour_depart=05&mois_depart=02&annee_depart=2012&jour_arrivee=05& mois_arrivee=02&annee_arrivee=2012&nb_nuit=13,> [2] You will see once you've clicked 'recalculate' it states breakfast is not included. This is INCORRECT – breakfast is included for all delegates. You do not need to add any additional breakfast to your room booking. Finally, you can see the developing schedule and other information on the Linaro Connect Q1.12 website here: ‧ Linaro Connect Q1.12 website <http://connect.linaro.org/events/event/lcq1-12/> [3] [1] http://connect.linaro.org/register-connect/ [2] http://www.sofitel.com/sofitel/lien_externe.svlt?goto=spec_rate_hotel&sub=IS P&code_hotel=0922&code_chaine=SOF&RA1=lin0502212&RA2=&ragp=0&libelle_tarif=1 &showEco=0&jour_depart=05&mois_depart=02&annee_depart=2012&jour_arrivee=05&m ois_arrivee=02&annee_arrivee=2012&nb_nuit=13, [3] http://connect.linaro.org/events/event/lcq1-12/ Regards, -- Arwen Donaghey Executive Assistant T: +44 1223 45 00 22 | M: +44 7791 279 521 Lockton House | Clarendon Road | Cambridge | CB2 8FH Linaro.org <http://www.linaro.org/> │ Open source software for ARM SoCs Follow Linaro: Facebook <http://www.facebook.com/pages/Linaro> | Twitter <http://twitter.com/#!/linaroorg> | Blog <http://www.linaro.org/linaro-blog/>

14 years, 1 month

[PATCH v2 0/4] Add SMDK5250 board support

by Chander Kashyap

This patchset add support for Samsung's SMDK5250 board based on EXYNOS5250 based SoC. It also adds support for MMC SPL booting. The porting is done by Samsung engineers at HQ in System LSI Team. I am contributing in upstreaming the code for the board. Based upon discussions following patches are dropped in this version: Exynos: Add CONFIG_EXYNOS4 Macro to EXYNOS4 based boards Exynos: Clock.c: Replace exynos4 prefix with exynos SMDK5250: enable device tree support is squashed with EXYNOS: Add SMDK5250 board support Chander Kashyap (4): Exynos: Clock.c: Use CONFIG_SYS_CLK_FREQ macro ARM: EXYNOS: Add support for Exynos5 based SoCs EXYNOS: Add SMDK5250 board support EXYNOS: SMDK5250: Add MMC SPL support MAINTAINERS | 1 + arch/arm/cpu/armv7/exynos/clock.c | 215 +++++++++- arch/arm/include/asm/arch-exynos/clock.h | 326 ++++++++++++++ arch/arm/include/asm/arch-exynos/cpu.h | 53 ++- arch/arm/include/asm/arch-exynos/gpio.h | 32 ++ board/samsung/smdk5250/Makefile | 64 +++ board/samsung/smdk5250/lowlevel_init.S | 528 ++++++++++++++++++++++ board/samsung/smdk5250/mem_setup.S | 600 +++++++++++++++++++++++++ board/samsung/smdk5250/mmc_boot.c | 58 +++ board/samsung/smdk5250/smdk5250.c | 125 +++++ board/samsung/smdk5250/smdk5250_setup.h | 589 ++++++++++++++++++++++++ board/samsung/smdk5250/tools/mkexynos_image.c | 117 +++++ boards.cfg | 1 + include/configs/s5pc210_universal.h | 1 + include/configs/smdk5250.h | 188 ++++++++ 15 files changed, 2878 insertions(+), 20 deletions(-) create mode 100644 board/samsung/smdk5250/Makefile create mode 100644 board/samsung/smdk5250/lowlevel_init.S create mode 100644 board/samsung/smdk5250/mem_setup.S create mode 100644 board/samsung/smdk5250/mmc_boot.c create mode 100644 board/samsung/smdk5250/smdk5250.c create mode 100644 board/samsung/smdk5250/smdk5250_setup.h create mode 100644 board/samsung/smdk5250/tools/mkexynos_image.c create mode 100644 include/configs/smdk5250.h -- 1.7.5.4

14 years, 1 month

Fwd: Errors in work item definitions

by Tony Mansson

Hi Guys. I get a lot of spam from launchpad whenever the format of a blueprint is not OK. Below is an example. Please don't use colons (as e.g. in an URL) inside work item definitions. There is a low-IQ parser somewhere that gets confused by that. BR, Tony ---------- Forwarded message ---------- From: Launchpad work item tracker < work-items-tracker-hackers(a)lists.launchpad.net> Date: 9 January 2012 13:37 Subject: Errors in work item definitions To: tony.mansson(a)linaro.org https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/tracking-panda/#build=139" for work item "https" https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/staging-imx53/#build=142" for work item "https" https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/landing-panda/#build=15" for work item "https" https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/landing-snowball/#build=113" for work item "https" https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/staging-panda/#build=184" for work item "https" https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-12.01-… [ERROR] invalid state "// android-build.linaro.org/builds/~linaro-android/staging-snowball/#build=154" for work item "https"

14 years, 1 month

Status reporting

by Tony Mansson

Hello Android Team. Tomorrows meeting page: https://wiki.linaro.org/Platform/Android/Meetings/2012-01-11 is now open for status reporting. BR, Tony

14 years, 1 month

← Newer
1
...
7
8
9
10
11
12
13
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev January 2012