linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[Android: device/linaro/beagleboard] Configure build to use u-boot

by Patrik Ryd

Introduced a alternative way of building u-boot instead of forcing u-boot to be built as if it was Androids 2ndbootloader. --- BoardConfig.mk | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/BoardConfig.mk b/BoardConfig.mk index 227f676..e538591 100644 --- a/BoardConfig.mk +++ b/BoardConfig.mk @@ -4,11 +4,12 @@ # TARGET_BOARD_PLATFORM := omap3 -TARGET_NO_BOOTLOADER := false +TARGET_NO_BOOTLOADER := true # Uses u-boot instead TARGET_NO_KERNEL := false KERNEL_CONFIG := android_omap3_defconfig +TARGET_USE_UBOOT := true UBOOT_CONFIG := omap3_beagle_config -INSTALLED_2NDBOOTLOADER_TARGET := $(PRODUCT_OUT)/u-boot.bin +TARGET_USE_XLOADER := false TARGET_NO_RECOVERY := true TARGET_NO_RADIOIMAGE := true TARGET_PROVIDES_INIT_RC := true -- 1.7.1

14 years, 1 month

[Android: device/linaro/pandaboard 1/3] Enable kernel

by Patrik Ryd

Set TARGET_NO_KERNEL to false in BoardConfig and use android_omap4_defconfig when building kernel. --- BoardConfig.mk | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/BoardConfig.mk b/BoardConfig.mk index 82a06bd..6b808e2 100644 --- a/BoardConfig.mk +++ b/BoardConfig.mk @@ -5,7 +5,8 @@ TARGET_BOARD_PLATFORM := omap4 TARGET_NO_BOOTLOADER := true -TARGET_NO_KERNEL := true +TARGET_NO_KERNEL := false +KERNEL_CONFIG := android_omap4_defconfig TARGET_NO_RADIOIMAGE := true TARGET_PROVIDES_INIT_RC := true BOARD_USES_GENERIC_AUDIO := false -- 1.7.1

14 years, 1 month

[Android: device/linaro/common] Building u-boot

by Patrik Ryd

Introduced a alternative way of building u-boot instead of forcing u-boot to be built as if it was Androids 2ndbootloader. --- tasks/bootfiles.mk | 12 ++++++++++++ tasks/kernel.mk | 1 - tasks/uboot.mk | 3 +-- 3 files changed, 13 insertions(+), 3 deletions(-) create mode 100644 tasks/bootfiles.mk diff --git a/tasks/bootfiles.mk b/tasks/bootfiles.mk new file mode 100644 index 0000000..8489e69 --- /dev/null +++ b/tasks/bootfiles.mk @@ -0,0 +1,12 @@ + +ifeq ($(TARGET_USE_UBOOT),true) +bootfiles: $(PRODUCT_OUT)/u-boot.bin +endif + +bootfiles: + $(hide) mkdir -p $(PRODUCT_OUT)/boot +ifeq ($(TARGET_USE_UBOOT),true) + cp $(PRODUCT_OUT)/u-boot.bin $(PRODUCT_OUT)/boot +endif + +$(INSTALLED_BOOTTARBALL_TARGET): bootfiles \ No newline at end of file diff --git a/tasks/kernel.mk b/tasks/kernel.mk index 8d4cabf..a016d6e 100644 --- a/tasks/kernel.mk +++ b/tasks/kernel.mk @@ -4,5 +4,4 @@ android_kernel: make ARCH=arm CROSS_COMPILE=../$(TARGET_TOOLS_PREFIX) uImage $(PRODUCT_OUT)/kernel: android_kernel - echo HUPP : $(PRODUCT_OUT) : $(TOP) : $(KERNEL_CONFIG) : $(PRODUCT_OUT)/kernel ln -sf ../../../../kernel/arch/arm/boot/uImage $(PRODUCT_OUT)/kernel \ No newline at end of file diff --git a/tasks/uboot.mk b/tasks/uboot.mk index 3d297c0..fc4a7da 100644 --- a/tasks/uboot.mk +++ b/tasks/uboot.mk @@ -1,6 +1,5 @@ android_uboot: - rm -fr $(PRODUCT_OUT)/obj/u-boot - mkdir $(PRODUCT_OUT)/obj/u-boot + mkdir -p $(PRODUCT_OUT)/obj/u-boot cd $(TOP)/u-boot &&\ make O=../$(PRODUCT_OUT)/obj/u-boot CROSS_COMPILE=arm-linux-gnueabi- $(UBOOT_CONFIG) &&\ make O=../$(PRODUCT_OUT)/obj/u-boot CROSS_COMPILE=arm-linux-gnueabi- -- 1.7.1

14 years, 1 month

Release critical and important bugs

by Jamie Bennett

Hi, As we near final release it is even more important that bugs which effect the LEB's and other images are caught early and fixed as soon as possible. To help aid the Linaro Release Team [1] in identifying and dealing with these types of bugs the following procedure significantly helps on projects which produce, or are installed on the images: 1) All bugs in a 'New' state should be sufficiently triaged to determine their 'Importance'. 2) All bugs which are deemed 'High' or 'Critical' should be highlighted to the Release Team. To do this use the 'Subscribe someone else' link on the right hand side of the bug. When the pop-up appears type 'linaro-release' into the box and select the release team when it is found. 3) If the bug needs discussion please add it to the wiki page for the current weeks Release meeting. The calendar for the Release meeting can be found at: https://wiki.linaro.org/Cycles/WeeklyReleaseMeeting Meetings are currently on a Thursday so add the bug to the 'Bugs' section of the next meeting. If possible please attend the meeting. The Release Team will go through the list of bugs [2] regularly and help to get fixes in place ready for milestone releases [3]. This information can also be found on the wiki at: https://wiki.linaro.org/Cycles/BugManagement Regards, Jamie. -- Linaro Release Manager | Platform Project Manager [1] https://launchpad.net/~linaro-release [2] https://bugs.launchpad.net/~linaro-release [3] https://wiki.linaro.org/Cycles/1105#Milestones

14 years, 1 month

Notes and actions from MM WG call on 5th April

by Sachin Gupta

Hi All, Please find enclosed link to minutes and actions for multimedia wg meeting on 5th April 2011. https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-04-05<https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-03-01><https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-02-22> Summary - first version of gstreamer plugin for AAC encoder uploaded to git - upstreaming of STE's vp8 decoder optimisations to be taken up - Feng Wei from Freescale joined multimedia working group Thanks Sachin

14 years, 1 month

Re: git merge question

by Jesse Barker

All these git related puns are killing me :-) On Fri, Apr 8, 2011 at 8:46 AM, Will Deacon <will.deacon(a)arm.com> wrote: > > On Fri, Apr 8, 2011 at 3:45 PM, Tixy <tixy(a)yxit.co.uk> wrote: > > > On Fri, 2011-04-08 at 10:16 +0100, Dave Martin wrote: > > >> one reason why my understanding of the actual problem here was a bit > > >> patchy. > > > > > > <groan> :-) > > > > _not_ intentional! (if you believe me) > > I don't believe you; I think you should consider branching out > into comedy... > > Will > > > > > _______________________________________________ > linaro-dev mailing list > linaro-dev(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev >

14 years, 1 month

[NOTES] Minutes & Actions: Toolchain Working Group meetings of Apr 04 & 07, 2011

by Mounir Bsaibes

Enclosed you'll find a link to the agenda, minutes and actions from the Linaro Toolchain working group weekly meetings of April 04 & 07, 2011. https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-04 https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-04-07 == Summary == * More vectoriser patches including if-conversion, different vector sizes, and vzip/vunzip are going upstream * Chung-Lin continues to knock off a good set of bugs * QEMU consolidation continues * A fair set of patches were accepted upstream recently * The OMAP3 patch set has been split further up. * A separate set of discussions on Thumb-2 performance improvements will start soon * Andrew is running a Linaro Android baseline build to prepare for the Android GCC patches later * Linaro GCC 4.6 is being updated to the new FSF 4.6 release branch * Cleaning up the libunwind testsuite for use exercising the ARM port Regards, Mounir

14 years, 1 month

[PATCH android/system/core] libpixelflinger: Add ARM NEON optimized scanline_t32cb16

by Jim Huang

Reference benchmark results on Beagleboard (TI OMAP353x) at 500 MHz: scanline_t32cb16_c memory bandwidth: 31.63 MB/s scanline_t32cb16_neon memory bandwidth: 147.69 MB/s It can dramatically improve the performance of boot animation. Code Review: https://review.source.android.com//#change,16358

14 years, 1 month

git merge question

by Dave Martin

Hi all, I've encountered a problem trying to unpick the history of the linaro git trees, but I don't think it's specific to us: The problem seems to be that when a merge is committed, git references the merged commits in their original context: no information is recorded about how the merge was resolved. The result just appears by magic as the new tree recorded for the merge commit. This seems to mean that git format-patch x..y (where x is an ancestor of y) does _not_ necessarily give you a patch series which actually applies on x (indeed, the generated patch series may not be appliable on any commit, in any order). This is certainly my experience. As a result, it seems very difficult to pick apart the history of a branch beyond the last merge commit, because the git repo only records the logical ancestry (i.e., which upstream patches got merged) rather than any "physical" history (i.e., what sequence of actual changes would be needed to reconstruct the branch). In fact, it seems to be nonsense to think in terms of a sequence of patches beyond a merge commit. What I'm actually trying to do is cherry-pick a few omap- and Thumb- specific commits out of the linaro tree to apply on v2.6.39-rc2 -- just the minimum subset so that I can develop Thumb stuff on a tree which is as clean and close to upstream as possible. But I repeatedly run into problems where patch p from branch b depends on cherry-picking some other patch q merged branch b, but the cherry pick fails since the actual delta recorded for q is in the context of someone else's branch (the branch that was merged from). If anyone knows a straightforward way to achieve this, I'd be interested ... Of course, I may be trying to do entirely the wrong thing. Cheers ---Dave

14 years, 1 month

[gwolf@debian.org: Registration now open for DebConf11]

by Steve McIntyre

FYI: ----- Forwarded message from Gunnar Wolf <gwolf(a)debian.org> ----- Date: Thu, 7 Apr 2011 14:16:33 -0500 From: Gunnar Wolf <gwolf(a)debian.org> To: debian-devel-announce(a)lists.debian.org Subject: Registration now open for DebConf11 User-Agent: Mutt/1.5.20 (2009-06-14) Registration is now open for DebConf11. For registration instructions, please see: http://debconf11.debconf.org/register.xhtml DebConf11 will take place in Banja Luka, in Republika Srpska, Bosnia and Herzegovina from Sunday 24th to Saturday 30th July, 2011. DebConf will be preceded by DebCamp, from Sunday 17th to Saturday 23rd July, 2011. DebCamp is a smaller, less formal event intended for group work on Debian projects. The sponsored registration deadline is 8 May. Again, this year, we will have basic, sponsored, professional (€450), and corporate (€1000) registration categories. Travel sponsorship is again available. ----- End forwarded message ----- Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org

14 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev