linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by Jon Smirl

The toolchain isn't built with -mcallee-super-interworking enabled. Could we get that turned on? It is needed to make calls to thumb code in ROM. arm-linux-gnueabi-gcc -g -DDEBUG -Os -fno-strict-aliasing -fno-common -ffixed-r8 -ffunction-sections -msoft-float -Wcast-align -Wall -D__KERNEL__ -DTEXT_BASE= -fno-builtin -ffreestanding -isystem /usr/lib/gcc/arm-linux-gnueabi/4.5.1/include -pipe -march=armv4t -mlong-calls -mtune=arm7tdmi-s -DCONFIG_ARM -D__ARM__ -mthumb-interwork -Wall -Wstrict-prototypes -Wcast-align -Wextra -Werror -Iobj_redbee-econotag_board -I../board -DBOARD=redbee-econotag -I../lib/include -I../src -I. -mthumb -mcallee-super-interworking -MMD -c -o obj_redbee-econotag_board/sleep.o sleep.c sleep.c:1:0: error: AAPCS does not support -mcallee-super-interworking -- Jon Smirl jonsmirl(a)gmail.com

14 years, 3 months

[PATCH] UBUNTU - ARM: adding i2c eeprom driver to read EDID

by Mathieu Poirier

All, This patch creates an entry in /sys that allows user space utilities such as 'decode-edid' and 'parse-edid' to read the monitor's EDID information. Please consider adding to your tree. Processor: Omap3 Platform: beagleboard Cx Mathieu. >From 7d0d86809864cb852988a296b12dff6436c45480 Mon Sep 17 00:00:00 2001 From: Mathieu J. Poirier <mathieu.poirier(a)canonical.com> Date: Fri, 20 Aug 2010 14:25:53 -0600 Subject: [PATCH] UBUNTU - ARM: adding i2c eeprom driver to read EDID Adding i2c eeprom driver to access monitor EDID binary information from user space, something that is required by 'decode-edid' and 'parse-edid'. BugLink: https://bugs.launchpad.net/bugs/608279 Signed-off-by: Mathieu Poirier <mathieu.poirier(a)canonical.com> --- arch/arm/mach-omap2/board-omap3beagle.c | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c index 7a1b351..fb6cbb9 100644 --- a/arch/arm/mach-omap2/board-omap3beagle.c +++ b/arch/arm/mach-omap2/board-omap3beagle.c @@ -355,13 +355,19 @@ static struct i2c_board_info __initdata beagle_i2c_boardinfo[] = { }, }; +static struct i2c_board_info __initdata beagle_i2c_eeprom[] = { + { + I2C_BOARD_INFO("eeprom", 0x50), + }, +}; + static int __init omap3_beagle_i2c_init(void) { omap_register_i2c_bus(1, 2600, beagle_i2c_boardinfo, ARRAY_SIZE(beagle_i2c_boardinfo)); /* Bus 3 is attached to the DVI port where devices like the pico DLP * projector don't work reliably with 400kHz */ - omap_register_i2c_bus(3, 100, NULL, 0); + omap_register_i2c_bus(3, 100, beagle_i2c_eeprom, ARRAY_SIZE(beagle_i2c_eeprom)); return 0; } -- 1.7.0.4

14 years, 3 months

PM support for OMAP

by Ameya Palande

Hi, AFAIU pm branch on linux-omap tree contains required patches, but they are not yet ready for inclusion in upstream kernel. How is linaro planning to provide pm support for TI omap[34] chips? Cheers, Ameya.

14 years, 3 months

Eclipse Day 2010

by Loïc Minier

Hey Slides from Eclipse Day 2010 were just published at: http://wiki.eclipse.org/Eclipse_Day_At_Googleplex_2010#Presentation_Slides I think we're lacking in developers tools ATM, and found some presentations interesting, the two I read in full were: Eclipse Linux Tools Project - Andrew Overholt (Red Hat) which I recommend and: Android Tools for Eclipse - Xavier Ducrohet (Google) which I don't recommend. Cheers -- Loïc Minier

14 years, 3 months

Restricting architectures

by Michael Hope

Hi there. We've been having a discussion in the Toolchain WG regarding Thumb-1 improvements. I want to decline doing them as I've assumed that Linaro is focused on the Cortex-A series, but I can't find that written down anywhere. May I limit the Toolchain WG to currently or nearly shipping Cortex-A implementations? This means: * Cortex-A profile only * ARMv7 only * ARM and Thumb-2 instruction sets * With or without NEON * With either VFPv3 D16 or D32 * With or without SMP We will try to do no harm to other architectures or earlier ARM versions. The Thumb-2 routines may be applicable to the Cortex-M and Cortex-R series but we will not optimise for them. I'd like Linaro to state this explicitly in the next round. https://wiki.linaro.org/Linaro1011/TechnicalRequirements defines a 'Standard ARMv7 Configuration' but there's no higher level statement justifying it, no statement restricting us to it, and it includes ARM, Thumb-2, and Thumb-1. -- Michael

14 years, 3 months

Profiling fixes for -stable

by Will Deacon

Hi Nicolas, If you're still accepting fixes for the 2.6.35 stable Linaro Kernel then I have some small profiling updates for you: The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51: Linus Torvalds (1): Linux 2.6.35 are available in the git repository at: git://repo.or.cz/linux-2.6/linux-wd.git for-linaro-stable Will Deacon (4): oprofile: don't call arch exit code from init code on failure ARM: oprofile: fix and simplify init/exit functions ARM: perf: reword comments relating to perf_event_do_pending ARM: perf: fix event validation arch/arm/include/asm/perf_event.h | 2 +- arch/arm/kernel/perf_event.c | 12 ++++---- arch/arm/oprofile/common.c | 47 +++++++++++++++++++----------------- drivers/oprofile/oprof.c | 11 +------- 4 files changed, 34 insertions(+), 38 deletions(-) Nothing groundbreaking, but worth having nonetheless. These guys are also sitting in my for-linaro branch but I'm hoping they'll be in 2.6.36 anyway. Cheers, Will

14 years, 3 months

per flavour linux-linaro source packages

by John Rigby

Tim, Building the three flavours of the linux-linaro kernel package currently takes over eleven hours. To improve that situation in the long term there are ideas about cross compiling in the build farm but that is still in the future. In the short term we would like to have multiple source packages. I have a script (attached) that tweaks the tree per flavour and runs debuild -S to produce one source package per flavour. I can include the script under debian/linaro/scripts for producing per platform sources or as an alternative I can have per flavour branches of the linux-linaro tree, probably produced by a similar script, that you could pull from and do the normal source generation per branch. Which of these do you prefer or do you have a third better idea? Thanks for your input. John

14 years, 3 months

imx51 and CONFIG_NEON

by John Rigby

Amit, Bryan: Do you know what the correct setting for CONFIG_NEON is for MX51? In a discussion on IRC there was mention that there is a patch that makes it safe to turn on. Do you know if that patch has made it upstream? Thanks, John

14 years, 3 months

Linaro Infrastructure Team Weekly Report (2010-08-26 to 2010-09-01)

by Ian Smith

The weekly report for the Linaro Infrastructure team may be found at: Status report:https://wiki.linaro.org/Platform/Infrastructure/Status/2010-08-26 Burndown chart:http://people.canonical.com/~pitti/workitems/maverick/linaro-infrastr… The burndown chart is showing that reasonable progress is being made against the work items, and the total number of work items hasn't changed, and progress is being made on the outstanding items to keep close to the trend line. * Abrek: Results command: Completed * Code reviews for some launch control branches * Added a wiki page about using the QA tracker * Further work on improving the hardware packs spec. * Worked on getting hwpack-create script going. * (arm-m-image-building-console): "Resolve timezone patch to django issue": DONE * (x-project-blueprint-references) -- nb. Launchpad spec, so not divvied up into workitems: DONE * arm-m-private-archive-hosting-infrastructure: Change to accept binary uploads: landed Please let me know if you have any questions. Kind Regards, Ian

14 years, 3 months

Linaro Beta Released

by Jamie Bennett

Hi, Another month, another release. Today sees the launch of the Linaro Beta image which will in-turn become the final release in November. The team have been working super-hard to ensure bugs are at a minimum whist bring in new exciting functionality. Highlights of this release include: * Support for the ARM Versatile Express platform which supplements the existing OMAP image. * Support is now available for OMAP Beagle Board C3/C4, OMAP Beagle Board XM, ARM Versatile Express, and with some modifications OMAP Panda Board, IGEPv2, Freescale iMX51. * Three new experimental seeds are available which enable the headless image to be supplemented by a particular install flavor: o linaro-netbook-efl - Netbook user interface using the EFL based netbook-launcher o linaro-alip - A reduced size installation, see http://linux.onarm.com/index.php/Main_Page for more details on ALIP o linaro-handset-plasma - A KDE/Plasma based user interface. * 35 upgraded packages since alpha-3. * Includes the 2.6.35 final kernel. * Tested using the new QA Tracking infrastructure located at http://qatracker.linaro.org/ More information on this development release as well as download and installation instructions can be found at: http://wiki.linaro.org/Releases/1011/Beta More information on Linaro in general and the 10.11 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 10.11: http://wiki.linaro.org/Releases/1011 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.freenode.net For any errata issues please see: http://wiki.linaro.org/Releases/1011/Beta#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager

14 years, 3 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev