linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[PATCH V4 0/5] Add MX51 basic DT support

by Jason Liu

From: Jason Liu <Jason Liu jason.hui(a)linaro.org> This patchset adds Freescale i.mx51 device tree support. This is based on git://git.secretlab.ca/git/linux-2.6 devicetree/test This patch has been tested on MX51 babbage board and can boot up succesfully to linux console with DT enabled. Grant, I think it's almost ready for you to merge it. V4: - Add Linaro sign off and copyrightt V3: - prefix the property name with the vendor name as like: "fsl,has-rts-cts" and "fsl,irda-mode" - use the ttymxc0 as the console - add FEC support, nfs can be used now Jason Liu (5): arm/dt: add basic mx51 device tree support arm/dt: add very basic dts file for babbage board serial/imx: parse from device tree support net/fec: check id_entry pointer before using it net/fec: add device tree matching support arch/arm/boot/dts/babbage.dts | 122 +++++++++++++++++++++++++++++++ arch/arm/mach-mx5/Kconfig | 8 ++ arch/arm/mach-mx5/Makefile | 1 + arch/arm/mach-mx5/board-dt.c | 65 ++++++++++++++++ arch/arm/mach-mx5/clock-mx51-mx53.c | 43 +++++++++++- arch/arm/plat-mxc/include/mach/common.h | 1 + drivers/net/fec.c | 25 +++++-- drivers/tty/serial/imx.c | 79 +++++++++++++++++--- 8 files changed, 327 insertions(+), 17 deletions(-) create mode 100644 arch/arm/boot/dts/babbage.dts create mode 100644 arch/arm/mach-mx5/board-dt.c

14 years, 1 month

Linaro 11.05 weekly testing 2011-03-17

by Jamie Bennett

Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ and our Community images: Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager

14 years, 1 month

linaro android build system issues

by Michael Hudson-Doyle

Hi all, For some reason the jenkins instance that powers the android build system isn't auto provisioning slaves from ec2, so builds are being queued but not executed. If you notice this happen and it's blocking you, get an admin (asac, loic, patryk) to go to https://android-build.linaro.org/jenkins/computer/ and click the "provision via ec2" button, and a slave will be started and run the builds. You can click it more than once to get multiple slaves to clear the queue more quickly. The slaves will be de-provisioned after they have been idle for a little while, so we don't need to manually clean up after ourselves. I'll try and figure out what's going on and fix it next week. Cheers, mwh

14 years, 1 month

[PATCH] only refresh when the clock tree is changed in debugfs

by yong.shen＠linaro.org

This patch is for working item "Allocate the data structures only once instead of at every refresh" at https://blueprints.edge.launchpad.net/linaro-pm-wg/+spec/a-new-tool-to-disp…. source code: http://git.linaro.org/gitweb?p=tools/powerdebug.git;a=summary git tree: git://git.linaro.org/tools/powerdebug.git

14 years, 1 month

a different fix for panda hang

by John Rigby

Nicolas, Today hrw pointed out this patch. It seems to be the proper fix for the panda hang. http://marc.info/?l=linux-omap&m=130021624629574&w=2 John

14 years, 1 month

[PATCH 0/5] add full platform dt clock support for mx51 babbage

by Shawn Guo

This patch set is to add full platform dt clock support for mx51 babbage, based on Jason's basic-mx51-dt patch. All mx51 non-dt clocks in clock-mx51-mx53.c are translated to dt ones. Shawn Guo (5): arm/dts: babbage: add all available clock nodes arm/mxc: add clk member 'rate' to ease dt fixed-clock support arm/dt: mx51: dynamically add clocks per dt nodes arm/dt: mx5: change timer init function to dt clock way of/clock: eliminate function __of_clk_get_from_provider arch/arm/boot/dts/babbage.dts | 495 +++++++++++- arch/arm/mach-mx5/board-dt.c | 9 +- arch/arm/mach-mx5/clock-mx51-mx53.c | 1401 +++++++++++++++++++++++++++++++- arch/arm/plat-mxc/include/mach/clock.h | 4 + drivers/of/clock.c | 23 +- 5 files changed, 1886 insertions(+), 46 deletions(-) Regards, Shawn

14 years, 1 month

LAVA integration effort for Android validation

by Jeremy Chang

Hi, list: I am working on Validation part for Android, in which mainly inclusive of integrating existing benchmark and testing suites into abrek, like 0xbench and android CTS. For now in my thought, if these benchmark/testing can integrate with abrek, then it should be no much problem or extra effort for integrating further into LAVA. Though I have some questions regarding to validation. How to detect the early fail through serial console? like detecting the failure during kernel booting stage also before running init or getting the shell. I think this will be a job issued by the dispatcher though I don't know how this checking mechanism will be done. Would there be anything here needed to do specifically for Android? How to connect the devices in the farm? I checked the wiki page, Platform/Validation/Specs/HardwareSetup [1]. The network will be used. I am thinking what's needed for setting up a network environment for this? The device is needed to fetch a fixed ip by dhcp just after booting up? USB gadget is an alternative for Android and in most situation could be more convenient for personal testing. adb (Android Debug Bridge, running on host side) can connect to a device through USB or TCP/IP. I suppose there are device context for describing how to connect certain device probably, like Android devices. Regarding to remote device registration, adb can list all the attached device but we still need a way to distinguish from each device in the farm. IP is a way to distinguish between each of them, like: $ adb devices List of devices attached emulator-5554 device 192.168.85.102:5555 device Any feedback is appreciated. Thanks. Regards, -Jeremy Chang [1] https://wiki.linaro.org/Platform/Validation/Specs/HardwareSetup

14 years, 1 month

[PATCH] arm/dt: Add dtb make rule

by Rob Herring

From: Rob Herring <rob.herring(a)calxeda.com> Add a make rule to compile dt blobs for ARM. Signed-off-by: Rob Herring <rob.herring(a)calxeda.com> --- arch/arm/Makefile | 3 +++ arch/arm/boot/Makefile | 6 ++++++ 2 files changed, 9 insertions(+), 0 deletions(-) diff --git a/arch/arm/Makefile b/arch/arm/Makefile index b49dea6..566763f 100644 --- a/arch/arm/Makefile +++ b/arch/arm/Makefile @@ -284,6 +284,9 @@ zImage Image xipImage bootpImage uImage: vmlinux zinstall install: vmlinux $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $@ +%.dtb: + $(Q)$(MAKE) $(build)=$(boot) MACHINE=$(MACHINE) $(boot)/$@ + # We use MRPROPER_FILES and CLEAN_FILES now archclean: $(Q)$(MAKE) $(clean)=$(boot) diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile index dcf323d..bb63922 100644 --- a/arch/arm/boot/Makefile +++ b/arch/arm/boot/Makefile @@ -13,6 +13,8 @@ MKIMAGE := $(srctree)/scripts/mkuboot.sh +DTC_FLAGS := -p 1024 + ifneq ($(MACHINE),) include $(srctree)/$(MACHINE)/Makefile.boot endif @@ -59,6 +61,10 @@ $(obj)/zImage: $(obj)/compressed/vmlinux FORCE endif +# Rule to build device tree blobs +$(obj)/%.dtb: $(src)/dts/%.dts + $(call cmd,dtc) + quiet_cmd_uimage = UIMAGE $@ cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \ -C none -a $(LOADADDR) -e $(STARTADDR) \ -- 1.7.1

14 years, 1 month

[PATCH] [android/devices/linaro/common] Correct permission, owner and group on files in the root tarball

by Patrik Ryd

Fix for LP #731780. --- tasks/mktarball.sh | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++ tasks/tarballs.mk | 4 ++- 2 files changed, 63 insertions(+), 1 deletions(-) create mode 100755 tasks/mktarball.sh diff --git a/tasks/mktarball.sh b/tasks/mktarball.sh new file mode 100755 index 0000000..622ff47 --- /dev/null +++ b/tasks/mktarball.sh @@ -0,0 +1,60 @@ +#!/bin/bash + +# This is a modified copy of build/tools/mktarball.sh + +# $1: path to fs_get_stats program +# $2: start dir +# $3: subdir to tar up (from $2) +# $4: target tar name +# $5: target tarball name (usually $(3).bz2) + +if [ $# -ne 5 ]; then + echo "Error: wrong number of arguments in cmd: $0 $* " + exit 1 +fi + +fs_get_stats=`readlink -f $1` +start_dir=`readlink -f $2` +dir_to_tar=$3 +target_tar=`readlink -f $4` +target_tarball=`readlink -f $5` + +cd $2 + +#tar --no-recursion -cvf ${target_tar} ${dir_to_tar} +rm ${target_tar} > /dev/null 2>&1 + +# do dirs first +subdirs=`find ${dir_to_tar} -type d -print` +files=`find ${dir_to_tar} \! -type d -print` +for f in ${subdirs} ${files} ; do + curr_perms=`stat -c 0%a $f` + [ -d "$f" ] && is_dir=1 || is_dir=0 + f2=`echo ${f#*/}` + new_info=`${fs_get_stats} ${curr_perms} ${is_dir} ${f2}` + new_uid=`echo ${new_info} | awk '{print $1;}'` + new_gid=`echo ${new_info} | awk '{print $2;}'` + new_perms=`echo ${new_info} | awk '{print $3;}'` +# echo "$f: dir: $is_dir curr: $curr_perms uid: $new_uid gid: $new_gid "\ +# "perms: $new_perms" + tar --no-recursion --numeric-owner --owner $new_uid \ + --group $new_gid --mode $new_perms -p -rf ${target_tar} ${f} +done + +if [ $? -eq 0 ] ; then + case "${target_tarball}" in + *.bz2 ) + bzip2 -c ${target_tar} > ${target_tarball} + ;; + *.gz ) + gzip -c ${target_tar} > ${target_tarball} + ;; + esac + success=$? + [ $success -eq 0 ] || rm -f ${target_tarball} + rm -f ${target_tar} + exit $success +fi + +rm -f ${target_tar} +exit 1 diff --git a/tasks/tarballs.mk b/tasks/tarballs.mk index e569e98..e6354fc 100644 --- a/tasks/tarballs.mk +++ b/tasks/tarballs.mk @@ -2,11 +2,13 @@ # Trigger build of tar balls for the linaro boards # +LINARO_MKTARBALL := device/linaro/common/tasks/mktarball.sh + ####### ## root tarball define build-roottarball-target $(hide) echo "Target root fs tarball:" $(INSTALLED_ROOTTARBALL_TARGET) - $(hide) $(MKTARBALL) $(FS_GET_STATS) \ + $(hide) $(LINARO_MKTARBALL) $(FS_GET_STATS) \ $(PRODUCT_OUT)/root . $(PRIVATE_ROOT_TAR) \ $(INSTALLED_ROOTTARBALL_TARGET) endef -- 1.7.1

14 years, 2 months

[PATCH 2/2 android/device/linaro/common] mount mmc partitions instead of mtd partitions

by Jeremy Chang

All partitions from mmc is expected. This depends on Jim Huang's patch "init: support mmc device mount" in android/system/core to work. Signed-off-by: Jeremy Chang <jeremy.chang(a)linaro.org> --- init.rc | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/init.rc b/init.rc index b6a92c5..a3f72e1 100644 --- a/init.rc +++ b/init.rc @@ -90,12 +90,12 @@ loglevel 3 write /dev/cpuctl/bg_non_interactive/cpu.shares 52 on fs -# mount mtd partitions - # Mount /system rw first to give the filesystem a chance to save a checkpoint - mount yaffs2 mtd@system /system - mount yaffs2 mtd@system /system ro remount - mount yaffs2 mtd@userdata /data nosuid nodev - mount yaffs2 mtd@cache /cache nosuid nodev +# mount mmc partitions + mount ext4 mmc@blk0p3 /system + mount ext4 mmc@blk0p3 /system ro remount + mount ext4 mmc@blk0p5 /cache + mount ext4 mmc@blk0p6 /data + mount ext4 mmc@blk0p7 /sdcard on post-fs # once everything is setup, no need to modify / -- 1.7.1

14 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev