linaro-dev February 2012

linaro-dev@lists.linaro.org

150 participants
147 discussions

[PATCH v8 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 | 214 +++++++++++++- arch/arm/include/asm/arch-exynos/clock.h | 326 +++++++++++++++++++++ arch/arm/include/asm/arch-exynos/cpu.h | 35 +++- arch/arm/include/asm/arch-exynos/dmc.h | 146 ++++++++++ arch/arm/include/asm/arch-exynos/gpio.h | 99 ++++++- arch/arm/include/asm/arch-exynos/tzpc.h | 52 ++++ board/samsung/smdk5250/Makefile | 58 ++++ board/samsung/smdk5250/clock_init.c | 202 +++++++++++++ board/samsung/smdk5250/dmc_init.c | 462 ++++++++++++++++++++++++++++++ board/samsung/smdk5250/lowlevel_init.S | 96 ++++++ board/samsung/smdk5250/mmc_boot.c | 58 ++++ board/samsung/smdk5250/setup.h | 451 +++++++++++++++++++++++++++++ board/samsung/smdk5250/smdk5250.c | 146 ++++++++++ board/samsung/smdk5250/tzpc_init.c | 48 +++ boards.cfg | 1 + include/configs/s5pc210_universal.h | 1 + include/configs/smdk5250.h | 197 +++++++++++++ include/configs/trats.h | 1 + tools/Makefile | 6 + tools/mksmdk5250spl.c | 119 ++++++++ 21 files changed, 2702 insertions(+), 17 deletions(-) create mode 100644 arch/arm/include/asm/arch-exynos/dmc.h create mode 100644 arch/arm/include/asm/arch-exynos/tzpc.h create mode 100644 board/samsung/smdk5250/Makefile create mode 100644 board/samsung/smdk5250/clock_init.c create mode 100644 board/samsung/smdk5250/dmc_init.c create mode 100644 board/samsung/smdk5250/lowlevel_init.S create mode 100644 board/samsung/smdk5250/mmc_boot.c create mode 100644 board/samsung/smdk5250/setup.h create mode 100644 board/samsung/smdk5250/smdk5250.c create mode 100644 board/samsung/smdk5250/tzpc_init.c create mode 100644 include/configs/smdk5250.h create mode 100644 tools/mksmdk5250spl.c -- 1.7.5.4

14 years

Connect sessions from the Android Platform Team

by Tony Mansson

14 years

Validation at the Linaro Connect

by Paul Larson

Interested in Validation and going to the Linaro connect? Here are some of the sessions already scheduled that you might be interested in on the Validation track: Automated bootloader testing in LAVA https://blueprints.launchpad.net/lava-dispatcher/+spec/linaro-validation-q1… Discuss what needs to be done still on celery, and usage https://blueprints.launchpad.net/lava-lab/+spec/linaro-validation-q112-lava… LAVA Server Admin tools https://blueprints.launchpad.net/lava-server/+spec/linaro-validation-q112-a… Discuss test plans for big.LITTLE https://blueprints.launchpad.net/lava-test/+spec/linaro-validation-q112-big… Monitoring and managing device health in LAVA https://blueprints.launchpad.net/lava-lab/+spec/linaro-validation-q112-devi… Additionally, here are some sessions in other tracks that you may like: Ubuntu LEB and LAVA: Current status and future planning for proper image testing and validation https://blueprints.launchpad.net/linaro-ubuntu/+spec/linaro-platforms-q112-… Linaro's Kernel CI Process discussion and Feedback https://blueprints.launchpad.net/linaro/+spec/linaro-kernel-ci-q112-discuss… End to End Demo of Enabling Something for LAVA https://blueprints.launchpad.net/linaro/+spec/linaro-training-q112-end-to-e… Make sure to check http://summit.linaro.org/lcq1-12/track/linaro-validation/throughout the week for changes and additions. If you are around in the afternoons and want to help out on LAVA development, or want help getting started in it, swing by the validation hacking sessions and talk to us. See you next week!

14 years

native gdb for Android

by Barry Song

Hi guys, I compile a native gdb using linaro 2011.10 by “./configure --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi”, and the gdb runs on arm target boards directly. # gdb GNU gdb (Linaro GDB) 7.3-2011.10 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-none-linux-gnueabi". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>. (gdb) I can use it to debug native programs on target boards directly. For example, attach process, set breakpoints, check registers and memory. One issue is I can't see multi-threads, for example: PID 646 is system_server by ps "646 1000 159m S system_server" Then I use gdb to attach it: # gdb attach 646 (gdb) info threads Id Target Id Frame * 1 process 646 "system_server" __ioctl () at bionic/libc/arch-arm/syscalls/__ioctl.S:15 as you see, “info threads” only shows one thread but there are several threads in system_server. But if I compile a new program based on glibc and gnu libthread, I can see multi-threads by the gdb. So my questions are: 1. Should I compile the native gdb using android toolchain and android bionic/libthread libraries? 2. Why can’t the current gdb capture multithreads for android processes? This question is actually about the theory for gdb to know multi-threads. In my opinion, both gnu and android use clone() to fork threads and threads in one process have same tgid in kernel and all threads return same getpid() value. Why not gdb just travel process lists to find multi-threads? Thanks Barry

14 years

[PATCH V6 0/7] add a generic cpufreq driver

by Richard Zhao

The driver is based on clock and regulator APIs and support single core and multi core ARM SoCs. For multi core, it assume all cores share the same clock and voltage. Thanks Arnd, Mark, Jamie, Shawn, Rob, for your review. Changes in V6: - add scaling_available_freqs Changes in V5: - add more comments - rename trans-latency to clk-trans-latency, and it only describe clk latency. Regulator latency is got from regulator_set_voltage_time. Changes in v4: - add depends on HAVE_CLK && OF && REGULATOR - add set_cpu_freq fail check - regulator_put wehn module exit - add pr_fmt and convert all printk to pr_xxx - use voltage range - comment and doc fix - add cpu_volts value pre-check in module init - add helpfull module parameter max_freq - remove compatible string check on Arnd's comment. - remove generic-cpufreq to clk-reg-cpufreq Changes in v3: - move adjusting smp loops_per_jiffy to arm common code, and also adjust global loops_per_jiffy. - remove adjusting loops_per_jiffy in imx and omap cpufreq drivers. - check compatible "generic-cpufreq" when module_init - change printk to pr_xxx - add generic-cpufreq DT binding doc Changes in v2: - add volatage change support - change '_' in property name to '-' - use initial value to calculate loops_per_jiffy - fix reading cpu_volts property bug - let cpufreq_frequency_table_cpuinfo routines handle cpu_freq_khz_max/min - don't change freq in arm_cpufreq_exit, because every core share the same freq. - use unsigned long describe frequency as much as possible. Because clk use unsigned long, but cpufreq use unsigned int. [PATCH V6 1/7] ARM: add cpufreq transiton notifier to adjust [PATCH V6 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate [PATCH V6 3/7] cpufreq: OMAP: remove loops_per_jiffy recalculate for [PATCH V6 4/7] cpufreq: add clk-reg cpufreq driver [PATCH V6 5/7] dts/imx6q: add cpufreq property [PATCH V6 6/7] arm/imx6q: register arm_clk as cpu to clkdev [PATCH V6 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ Thanks Richard

14 years

[Activity] Toolchain WG Weekly Status report for week ending 2012-02-03

by Mounir Bsaibes

Enclosed please find the link to the Weekly Status report & meeting minutes for the Toolchain working group for the week ending 2012-02-03 == Weekly Status Report == https://wiki.linaro.org/WorkingGroups/ToolChain/Status/2012-02-02 == Meeting Minutes == https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-02-02 == Weekly Activity report == https://wiki.linaro.org/WorkingGroups/ToolChain/ActivityReports/2012-01-27 == Summary == (For details, see the Weekly Status Report, Meeting Minutes and Weekly Activity reports) * Roadmap / Connect * Completed End of quarter 2011Q4 reports * Set the sessions for Connect * Plan for 2012Q1 https://wiki.linaro.org/MichaelHope/Sandbox/Q1.12Plans * 64-bit * Submitted work on 64-bit shift in core registers patches upstream, awaiting review. * libunwind * Reviewed a patch from T. R. of Nokia who provided a bugfix in case unwind instructions are popping VFP registers * OpenEmbedded * Changed Qt build to respect the optimization flags * Wrote a script around QEMU to measure the memory footprint using named pipes to communicate with the serial console of the guest * GDB * Committed follow-on patch to fix cosmetic issues resulting from the remote "info proc" patch set. * GCC * Created 4.6 backport branch including subreg forward- propagation branch, the modes-tieable patch, and the combine.c regression fix, and evaluated for correctness and performance. * Investigated Ramana's vld1 patches, and a problem with excessive vmov's in the PR 51819 test case pointed out by Ramana. * QEMU * Wrote patches for the A15 Fast Models boot-wrapper that allow you to pass the kernel/initrd/kernel command line via a parameter to the model rather than having to hard code them into an ELF file along with the boot-wrapper. * target-arm/arm-devs queues pushed upstream [Calxeda Highbank model is now in upstream QEMU] * KVM * Sorted out a Debian fs to use for KVM guest : this is needed because the kernel module doesn't do Thumb or VFP yet. * Wrote wiki pages on how to reproduce the KVM prototype https://wiki.linaro.org/PeterMaydell/KVM/HowTo * Upstream patch review, many complicated things landing * Reviewed KVM ARM patches from Christoffer * Benchmarking * Continued benchmarking gcc-4.7 against gcc-linaro-4.6-2012.01 and gcc-4.6 with -o2 and -o3 variants, both with neon enabled. Best regards, Mounir -- Mounir Bsaibes Project Manager Follow Linaro.org: facebook.com/pages/Linaro/155974581091106 http://twitter.com/#!/linaroorg http://www.linaro.org/linaro-blog <http://www.linaro.org/linaro-blog>

14 years

Efika MX Smartbook + serial dongle needed at Linaro Connect

by Marcin Juszkiewicz

Hi Looks like I managed to break serial port on my Efika MX Smartbook today. As there are people in Linaro with this device I am asking for help. For this I need someone with Efika MX Smartbook and debug board to be present at conference. I will take my netbook and dongle so will be able to check is it dongle or Efika which broke for me. If you have both and have no use for them I can take it from you - will have no problems finding someone here wanting to play & hack on Efika ;)

14 years

[ACTIVITY] Multimedia WG weekly report - wk05.2012 (20120130-20120203)

by Ilias Biris

Hello! Please find below the summary of the weekly report for Multimedia WG, the full version of which (with links and detail) is in https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/WeeklyReport The last meeting minutes are in https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2012-01-31 For Connect, there are a number of sessions related to tackling audio issues, as well as a session on codecs, display api, tiny-sphinx (audio recognition) and tinyalsa. See the sessions in https://blueprints.launchpad.net/sprints/lcq1-12?searchtext=linaro-gfxmm and join the group to discuss! Tom has also been keeping a day-to-day plan of activities in https://wiki.linaro.org/TomGall/DraftPlan/20121QLC == Highlights == - Built and configured a working audio stack on panda/Ubuntu desktop - verified and closed defect 893402, worked on porting and debugging e2eaudiotest to panda, and finished also blueprint https://blueprints.launchpad.net/linaro-multimedia-project/+spec/engr-mm-au… - Libav AAC-SBR optimisations committed upstream with AAC-PS optimisation underway - v4l2+dmabuf+dri2video demo working - For DRM : dri2video cleanup and patches - Continued tinyalsa/tinyhardware work for UCM - Wrote ION documentation - https://wiki.linaro.org/BenjaminGaignard/ion - Update work for cma-test to use CMA v19 == Issues == - #880173 - Audio does not work on Upstream Panda - #889844 - Audio on HDMI is not working on trackin-panda - Fix Released from Landing Team remaining issue seems to be Android userland - #908957 - ICS: All arches: No aplay / arecord or equivalent - #911860 Android NEON detection is busticated - Triaged == Risks == - Risk of some Android-related Multimedia blueprints not finishing on time due to bugs #880173, #889844, #908957 (and the fact that time is short till the component release) - LJT - support upstream 1.2 blueprint could be delayed since upstream v1.2 source has to be tagged and released first BR, -- Ilias Biris ilias.biris(a)linaro.org Project Manager, Linaro M: +358504839608, IRC: ibiris Skype: ilias_biris Linaro.org│ Open source software for ARM SoCs

14 years

Re: Linaro Android against vanilla linux kernel versions

by Paul Sokolovsky

Hello Tugrul, On Fri, 3 Feb 2012 10:00:56 +0200 "Guclu, Tugrul" <tugrul.guclu(a)siemens.com> wrote: > Hi Paul > > Thanks for your answer. That was what I'm looking for. I got 2 more > questions if you would mind. > > 1) > All Android buils are available here > https://android-build.linaro.org/#builds=all ,correct ? Yes, both official monthly releases and daily releases are available there, old dailies are expired in 3 months though (release stay all the time). > If that is the case the oldest belongs to > ~linaro-android/panda-11.04-release 2011-04-28 15:28:40 Yes, 2011.04 was apparently first official Linaro Android release, and Linaro started working on Android not long before that. > 2) this is from ym download script > /repo init -u git://android.git.linaro.org/platform/manifest.git -b > linaro_android_2.3.5 > --repo-url=git://android.git.linaro.org/tools/repo.git -b gingerbread > || exit 1 > Where can I find the pinned manifest of linaro_android_2.3.5 ? Because > this build is not displayed in the > https://android-build.linaro.org/#builds=all ? Pinned manifests come for specific builds. The earliest release build for imx35 appears to be https://android-build.linaro.org/builds/~linaro-android/leb-imx53-11.07-rel… , and from a quick look that's even 2.3.4. Not sure about the kernel though, please check yourself - even though it's 2.3.4, we might have used much newer kernel than AOSP 2.3.4 (well, that's what Linaro does - leverages and tests newer technologies so vendors and community were more comfortable with adopting them). > BR > > Tugrul > -- Best Regards, Paul 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

[RFC] Upcoming work view for individual engineers

by Guilherme Salgado

Hi folks, We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them? Cheers, -- Guilherme Salgado <https://launchpad.net/~salgado>

14 years

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev February 2012