linaro-dev February 2011

linaro-dev@lists.linaro.org

120 participants
166 discussions

Board Support Review deadline this Thursday 24th February

by Jamie Bennett

Hi, Along with Feature Freeze [1], Thursday sees Linaro's Board Support Review deadline. This deadline marks the start of the process to define exactly what hardware will be enabled in the final Linaro Evaluation Builds released at the end of the cycle [2]. This review is to ensure that the target hardware support is progressing as expected and that the final user experience will shine on these boards. For more information on the Board Support Review deadline please see the Linaro wiki at: https://wiki.linaro.org/Process/Cycle/BoardReview There will be another review on 2011-03-24 where the list will be refined if necessary. A list of boards that Linaro expects to enable this cycle will be circulated after the review. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager Office: +44 1761 348 220 | Mobile: +44 7962 259 437 [1] http://lists.linaro.org/pipermail/linaro-dev/2011-February/002702.html [2] https://wiki.linaro.org/Releases/1105

13 years, 10 months

[PATCH, android device/linaro/common.git] Added target roottarball

by Patrik Ryd

>From e2ce2661169a8653c86112d4dd0d5ac99fbe6925 Mon Sep 17 00:00:00 2001 From: Patrik Ryd <patrik.ryd(a)linaro.org> Date: Mon, 21 Feb 2011 09:49:56 +0100 Subject: [PATCH] Added target roottarball The new taget roottarball creates a tarball of the root file system. --- tasks/tarballs.mk | 25 +++++++++++++++++++++++++ 1 files changed, 25 insertions(+), 0 deletions(-) create mode 100644 tasks/tarballs.mk diff --git a/tasks/tarballs.mk b/tasks/tarballs.mk new file mode 100644 index 0000000..e569e98 --- /dev/null +++ b/tasks/tarballs.mk @@ -0,0 +1,25 @@ +# +# Trigger build of tar balls for the linaro boards +# + +####### +## root tarball +define build-roottarball-target + $(hide) echo "Target root fs tarball:" $(INSTALLED_ROOTTARBALL_TARGET) + $(hide) $(MKTARBALL) $(FS_GET_STATS) \ + $(PRODUCT_OUT)/root . $(PRIVATE_ROOT_TAR) \ + $(INSTALLED_ROOTTARBALL_TARGET) +endef + +ifndef ROOT_TARBALL_FORMAT + ROOT_TARBALL_FORMAT := bz2 +endif + +root_tar := $(PRODUCT_OUT)/root.tar +INSTALLED_ROOTTARBALL_TARGET := $(root_tar).$(ROOT_TARBALL_FORMAT) + +$(INSTALLED_ROOTTARBALL_TARGET): PRIVATE_ROOT_TAR := $(root_tar) +$(INSTALLED_ROOTTARBALL_TARGET): $(FS_GET_STATS) $(INTERNAL_RAMDISK_FILES) + $(build-roottarball-target) + +roottarball: $(INSTALLED_ROOTTARBALL_TARGET) \ No newline at end of file -- 1.7.1

13 years, 10 months

Please reply if you got a U8500 board

by Per Forlin

Hi, Dave told me he got 3 u8500 boards but no UART break out board. From what I have heard the u8500 boards for Linaro should come with a full kit including power supply and UART. If you have a u8500 board please let me know if it contains a UART break out board or whether it is missing. Thanks, Per

13 years, 10 months

Feature Freeze this Thursday 24th February

by Jamie Bennett

Hi, Thursday 24th February is Feature Freeze. This is a point in the Engineering Cycle [1] where we stop taking new features and concentrate on fixing bugs. Please get your new features (as defined by new packages, API changes, additional features) proposed and uploaded to the archive as soon as possible. If you know of any features that will not make the deadline please make the Release Manager (me) aware of these and be prepared for the Feature Freeze Exception Process, an explanation of which can be found at: https://wiki.linaro.org/Process/Cycle/FreezeExceptionProcess To read more about the Feature Freeze deadline head on over to: https://wiki.linaro.org/Process/Cycle/FeatureFreeze Regards, Jamie. -- Linaro Release Manager [1] https://wiki.linaro.org/Releases/1105/Schedule

13 years, 10 months

Notes & Actions: Linaro Graphics Working Group - Feb 16, 2011

by Alexandros Frantzis

Hi, notes and actions from our Wednesday graphics working group call are available on the wiki: + https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2011-02-16 Details about when and where of this meeting can be found here: + https://wiki.linaro.org/WorkingGroups/Middleware/Graphics#Weekly%20Public%2… Summary ======= * cairo-gles: Patchset "EGL fixes" sent upstream for review: http://lists.cairographics.org/archives/cairo/2011-February/021687.html * cairo-gles: Work in progress for replacing remaining GL only features (GL_CLAMP_TO_BORDER, 1D Textures). * kwin: Succeed to run kwin on imx51 and fixed flickering issue, patch accepted by kwin upstream: http://commits.kde.org/kde-workspace/341d4f90b7e45f92813d8362ff21c6f4b7ba96… * Jammy got KDE developer account (thanks to Martin) * drm/mali: Verified that Mali drivers worked with sample 3D application on Linaro kernel. * compiz-gles: Immediate mode replaced with vertex arrays. * compiz-gles: rendering now using shaders with built-in variables (replacement of built-ins in progress) Thanks, -- - Alexandros

13 years, 10 months

Subject: [PATCH] Added target roottatball

by Patrik Ryd

>From 0af38129a04da9c7b621ba0bde2bd90980ad9756 Mon Sep 17 00:00:00 2001 From: Patrik Ryd <patrik.ryd(a)linaro.org> Date: Mon, 21 Feb 2011 09:49:56 +0100 Subject: [PATCH] Added target roottatball The new taget roottarball creates a tarball of the root file system. --- tasks/tarballs.mk | 25 +++++++++++++++++++++++++ 1 files changed, 25 insertions(+), 0 deletions(-) create mode 100644 tasks/tarballs.mk diff --git a/tasks/tarballs.mk b/tasks/tarballs.mk new file mode 100644 index 0000000..0c51644 --- /dev/null +++ b/tasks/tarballs.mk @@ -0,0 +1,25 @@ +# +# Trigger build of tar balls for the linaro boards +# + +####### +## root tarball +define build-roottarball-target + $(hide) echo "Target root fs tarball:" $(INSTALLED_ROOTTARBALL_TARGET) + $(hide) $(MKTARBALL) $(FS_GET_STATS) \ + $(PRODUCT_OUT) root $(PRIVATE_ROOT_TAR) \ + $(INSTALLED_ROOTTARBALL_TARGET) +endef + +ifndef ROOT_TARBALL_FORMAT + ROOT_TARBALL_FORMAT := bz2 +endif + +root_tar := $(PRODUCT_OUT)/root.tar +INSTALLED_ROOTTARBALL_TARGET := $(root_tar).$(BOOT_TARBALL_FORMAT) + +$(INSTALLED_ROOTTARBALL_TARGET): PRIVATE_ROOT_TAR := $(root_tar) +$(INSTALLED_ROOTTARBALL_TARGET): $(FS_GET_STATS) $(INTERNAL_RAMDISK_FILES) + $(build-roottarball-target) + +roottarball: $(INSTALLED_ROOTTARBALL_TARGET) \ No newline at end of file -- 1.7.1

13 years, 10 months

[PATCH] Added generic hook for loading device specific tasks.

by Patrik Ryd

>From 67fed63cd8449bea6f8704c66646ca9e26fe24e3 Mon Sep 17 00:00:00 2001 From: Patrik Ryd <patrik.ryd(a)linaro.org> Date: Mon, 14 Feb 2011 15:29:58 +0100 Subject: [PATCH] Added generic hook for loading device specific tasks. Change-Id: I6216195edd6a43e940b3d254256092aca98ca58d Signed-off-by: Patrik Ryd <patrik.ryd(a)linaro.org> --- core/Makefile | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/core/Makefile b/core/Makefile index d60723e..8c50fb7 100644 --- a/core/Makefile +++ b/core/Makefile @@ -1402,4 +1402,5 @@ $(INTERNAL_FINDBUGS_HTML_TARGET): $(INTERNAL_FINDBUGS_XML_TARGET) # ----------------------------------------------------------------- # These are some additional build tasks that need to be run. include $(sort $(wildcard $(BUILD_SYSTEM)/tasks/*.mk)) --include $(sort $(wildcard vendor/*/build/tasks/*.mk)) +include $(sort $(wildcard vendor/*/build/tasks/*.mk)) +include $(sort $(wildcard device/*/common/tasks/*.mk)) -- 1.7.1

13 years, 10 months

[PATCH v5 0/5] ARM: omap[34]: Thumb-2 compatibility fixes

by Dave Martin

This set of patches, along with some other patches under discussion on alkml, should enable omap3 and omap4 kernels to be built with CONFIG_THUMB2_KERNEL. This patch set builds on recent cleanup done by the omap maintainers. At least some of this code definitely works, most features have been tested successfully. Further testing, especially of Thumb-2 behaviour, is still welcome. Seems to work with CONFIG_SMP_ON_UP and CONFIG_THUMB2_KERNEL enabled on Beagle xM A2 and Panda A1. Thanks also to Santosh Shilimkar and Kevin Hilman for their help with testing. v3: * make SMC instruction syntax more consistent * remove do_wfi() in favour of the generic wfi() macro v4: * revert to the OMAP-specific do_wfi() implementation, pending discussion of how generic macros can/should be provided v5: * use ARM for low-level code in mach-omap2/*34xx.S, for correct interoperation with non-Thumb-capable firmware. I've stripped the Acked/Tested-bys from the major patches to mach-omap2/*34xx.S, since the reversion to ARM constitutes a significant change -- I would be grateful if people could re- test / re-review if they have the chance. For best future compatibility, I've left the changes which avoid architecturally deprecated features. Details below. Cheers, Dave The patches can be found, along with a buildable working tree, in the following repo: git://git.linaro.org/people/dmart/linux-2.6-arm.git * arm/omap-thumb2: has the patches proposed here * arm/omap-thumb2+merged: additionally has some patches cherry- picked from other trees which are needed in order for the patches on arm/omap-thumb2 to work usefully. * dirty/arm/omap-thumb2+merged: buildable test tree, which adds 2 local patches to work around a toolchain bug. A working kernel config for this tree is here: http://people.linaro.org/~dmart/arm_omap-thumb2+v2_config : CONFIG_SMP_ON_UP=y CONFIG_THUMB2_KERNEL=y CONFIG_SERIAL_OMAP=y (to avoid garbage on xM; for Panda use console=ttyS2) (The config is derived from the linaro omap config and so turns on loads of modules -- don't feel you have to build them all...) Cherry-picked patches originated from Russell's devel tree and Tony Lindgren's omap-testing tree: http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git devel git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-testing This series also depends on one un-merged patch to generic-ise the wfi() macro: git://git.linaro.org/people/dmart/linux-2.6-arm.git arm/wfi-macro Dave Martin (5): ARM: omap4: Provide do_wfi() for Thumb-2 ARM: omap4: Convert END() to ENDPROC() for correct linkage with CONFIG_THUMB2_KERNEL ARM: omap3: Remove hand-encoded SMC instructions ARM: omap3: Thumb-2 compatibility for sram34xx.S ARM: omap3: Thumb-2 compatibility for sleep34xx.S arch/arm/mach-omap2/include/mach/omap4-common.h | 4 ++ arch/arm/mach-omap2/omap-headsmp.S | 2 +- arch/arm/mach-omap2/omap44xx-smc.S | 8 ++-- arch/arm/mach-omap2/sleep34xx.S | 62 ++++++++++++++++++---- arch/arm/mach-omap2/sram34xx.S | 36 ++++++++++--- 5 files changed, 87 insertions(+), 25 deletions(-)

13 years, 10 months

Re: [PATCH] i.MX23/28 framebuffer driver

by Arnd Bergmann

On Wednesday 09 February 2011, Sascha Hauer wrote: > The driver patch itself is Cced to linux-fbdev, only the introductory > mail is not. Ok, I see. > > Did you consider making the driver a KMS driver instead of > > a frame buffer? I think the recommendation these days is > > to start out with KMS for new drivers, which will be somewhat > > simpler and give you a frame buffer device as well. I don't > > think that there is a need to change over any drivers from > > fb to kms though, since you've already done the work. > > I tried doing so for the i.MX51 which supports multiple displays on dvi > and vga outputs and thus could make good use of KMS and friends. Anyway, > I got stuck quite fast. The KMS stuff is tightly coupled with DRM/DRI > and needs many many callbacks to implement. Additionally the userspace > tools expect a nvidia/amd/intel driver and do not have a generic > fallback. I think this stuff is good for implementing a full blown > graphics driver, but is lacking support for simple framebuffer grapics. > I'd love to go this way but it still requires a lot of work. Ok. This sounds like a lot of upfront work indeed, to make KMS more generic, though I think a number of driver would benefit from it eventually. It could be something for the Linaro graphics working group to look at in the following 11.11 release, depending on how many other people are interested in getting there. Arnd

13 years, 10 months

Nice tool: chdist

by Michael Hope

Hi everyone. Loic pointed me at 'chdist', a nice tool that makes working with different releases much easier. You can use it to poke into and download packages from different releases without setting up a chroot for each one. I use from my Maverick host to grab the source packages from Natty when trying to track down a bug. For example, I'm looking into adding cortex-strings into the Natty libc6. Tell chdist about Natty by running: chdist create natty Update the list of packages using: chdist apt-get natty update Check which version is currently uploaded: chdist apt-cache natty show libc6 Grab the source: chdist apt-get natty source libc6 The distributions and configuration files end up under ~/.chdist such as ~/.chdist/natty/etc/apt/. -- Michael

13 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev February 2011