linaro-toolchain January 2012

linaro-toolchain@lists.linaro.org

21 participants
71 discussions

Linaro GCC 4.6 and 4.5 2012.01 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2012.01 release of Linaro GCC 4.6 and Linaro GCC 4.5. No changes were made in Linaro GDB this month and, as such, no release has been made. Linaro GCC 4.6 2012.01 is the eleventh release in the 4.6 series. Based off the latest GCC 4.6.2+svn182894 release, it contains a few bug fixes from over the Christmas break. Interesting changes include: * Updates to 4.6.2+svn182894 Fixes: * PR51301 ICE in vectorised widening multiplies * LP: #897583 Code generation bug with -O2 (-foptimize-sibling-calls) * LP: #736661 armel FTBFS due to compiler ICE Linaro GCC 4.5 2012.01 is the seventeenth release in the 4.5 series. Interesting changes include: * Updates to 4.5.3+svn182893 Fixes: * LP: #736661 armel FTBFS due to compiler ICE The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.6-2012.01 https://launchpad.net/gcc-linaro/+milestone/4.5-2012.01 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.6/4.6-2012.01 https://launchpad.net/gcc-linaro/4.5/4.5-2012.01 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? inquire at support(a)linaro.org -- Michael

13 years, 9 months

Linaro QEMU 2012.01 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2012.01. Linaro QEMU 2012.01 is the latest monthly release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. New in this month's release: - Several bug fixes which reinstate support for running on ARM hosts - Support for previously missing *xattr syscalls in usermode emulation - A (dummy) model of the L2x0/PL310 L2 cache contrnoller (thanks to Rob Herring and Mark Langsdorf of Calxeda) Known issues: - Graphics do not work for OMAP3 based models (beagle, overo) with 11.10 Linaro images. The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2012.01 More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro

13 years, 10 months

[PATCH 1/1] hw: Add IGEPv2 board support

by Javier Martinez Canillas

Add ISEE IGEPv2 board definition (an OMAP3730 based board). Signed-off-by: Javier Martinez Canillas <javier(a)dowhile0.org> --- Makefile.target | 2 +- hw/igep.c | 123 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 124 insertions(+), 1 deletions(-) create mode 100644 hw/igep.c diff --git a/Makefile.target b/Makefile.target index 409748f..2923dd7 100644 --- a/Makefile.target +++ b/Makefile.target @@ -349,7 +349,7 @@ obj-arm-y += omap1.o omap_lcdc.o omap_dma.o omap_clk.o omap_mmc.o omap_i2c.o \ obj-arm-y += omap2.o omap_dss.o soc_dma.o omap_gptimer.o omap_synctimer.o \ omap_gpmc.o omap_sdrc.o omap_spi.o omap_tap.o omap_l4.o obj-arm-y += omap3.o omap_usb.o omap3_boot.o omap3_mmc.o dsi.o -obj-arm-y += twl4030.o beagle.o overo.o +obj-arm-y += twl4030.o beagle.o overo.o igep.o obj-arm-y += omap_sx1.o palm.o tsc210x.o obj-arm-y += nseries.o blizzard.o onenand.o vga.o cbus.o tusb6010.o usb-musb.o obj-arm-y += mst_fpga.o mainstone.o diff --git a/hw/igep.c b/hw/igep.c new file mode 100644 index 0000000..5254ddf --- /dev/null +++ b/hw/igep.c @@ -0,0 +1,123 @@ +/* + * ISEE IGEPv2 board emulation. + * + * Copyright (c) 2012 ISEE 2007, SL + * Written by Javier Martinez Canillas (based on Gumstix Overo emulation code) + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License along + * with this program; if not, see <http://www.gnu.org/licenses/>. + */ + +#include "qemu-common.h" +#include "sysemu.h" +#include "omap.h" +#include "arm-misc.h" +#include "boards.h" +#include "i2c.h" +#include "net.h" +#include "devices.h" +#include "flash.h" +#include "sysbus.h" +#include "blockdev.h" +#include "exec-memory.h" + +#define IGEP_NAND_CS 0 +#define IGEP_NET_CS 5 + +struct igep_s { + struct omap_mpu_state_s *cpu; + + DeviceState *nand; + void *twl4030; + DeviceState *eth; + DeviceState *ddc; +}; + +static void igep_init(ram_addr_t ram_size, + const char *boot_device, + const char *kernel_filename, + const char *kernel_cmdline, + const char *initrd_filename, + const char *cpu_model) +{ + MemoryRegion *sysmem = get_system_memory(); + struct igep_s *s = (struct igep_s *) g_malloc0(sizeof(*s)); + DriveInfo *dmtd = drive_get(IF_MTD, 0, 0); + DriveInfo *dsd = drive_get(IF_SD, 0, 0); + + if (ram_size > 1024 * 1024 * 1024) { + fprintf(stderr, "igep: maximum permitted RAM size 1024MB\n"); + exit(1); + } + + if (!dmtd && !dsd) { + hw_error("%s: SD or NAND image required", __func__); + } + s->cpu = omap3_mpu_init(sysmem, omap3630, ram_size, + NULL, NULL, serial_hds[0], NULL); + + s->nand = qdev_create(NULL, "onenand"); + qdev_prop_set_uint16(s->nand, "manufacturer_id", NAND_MFR_STMICRO); + qdev_prop_set_uint16(s->nand, "device_id", 0x40); + qdev_prop_set_uint16(s->nand, "version_id", 0x121); + qdev_prop_set_int32(s->nand, "shift", 1); + if (dmtd && dmtd->bdrv) { + qdev_prop_set_drive_nofail(s->nand, "drive", dmtd->bdrv); + } + qdev_init_nofail(s->nand); + omap_gpmc_attach(s->cpu->gpmc, IGEP_NAND_CS, + sysbus_mmio_get_region(sysbus_from_qdev(s->nand), 0)); + + if (dsd) { + omap3_mmc_attach(s->cpu->omap3_mmc[0], dsd->bdrv, 0, 0); + } + + /* FAB revs >= 2516: 4030 interrupt is GPIO 0 (earlier ones were 112) */ + s->twl4030 = twl4030_init(omap_i2c_bus(s->cpu->i2c, 0), + qdev_get_gpio_in(s->cpu->gpio, 0), + NULL, NULL); + + /* Wire up an I2C slave which returns EDID monitor information; + * newer Linux kernels won't turn on the display unless they + * detect a monitor over DDC. + */ + s->ddc = i2c_create_slave(omap_i2c_bus(s->cpu->i2c, 2), "i2c-ddc", 0x50); + + omap_lcd_panel_attach(s->cpu->dss); + + /* Strictly this should be a LAN9221 */ + if (nd_table[0].vlan) { + /* The ethernet chip hangs off the GPMC */ + NICInfo *nd = &nd_table[0]; + qemu_check_nic_model(nd, "lan9118"); + s->eth = qdev_create(NULL, "lan9118"); + qdev_set_nic_properties(s->eth, nd); + qdev_init_nofail(s->eth); + omap_gpmc_attach(s->cpu->gpmc, IGEP_NET_CS, + sysbus_mmio_get_region(sysbus_from_qdev(s->eth), 0)); + sysbus_connect_irq(sysbus_from_qdev(s->eth), 0, + qdev_get_gpio_in(s->cpu->gpio, 176)); + } +} + +QEMUMachine igep_machine = { + .name = "igep", + .desc = "ISEE IGEPv2 board (OMAP3730)", + .init = igep_init, +}; + +static void igep_machine_init(void) +{ + qemu_register_machine(&igep_machine); +} + +machine_init(igep_machine_init); -- 1.7.4.1

13 years, 10 months

First proposals

by Michael Hope

Hi Åsa. Well, the first proposals have arrived. I've cc'ed this to linaro-toolchain so we have a record. First, visit: http://ex.seabright.co.nz/helpers/proposals and see there are new merge requests from Ulrich with new results. Next, login: http://ex.seabright.co.nz/helpers/login Your login is your Launchpad OpenID login "https://launchpad.net/~asa-sandahl" After logging in, go back to the proposals page. See that the fwprop-subreg merge request has a i686 and x86_64 result. The i686 one is fine so click 'Record' and follow your nose. The x86_64 is interesting - the fault might be real. Click 'Record'. Note the subject line has 'regressed' in it. Ulrich will have to investigate. The lp-879725 results look fine so record both of those. Scanning down the page shows that everything else is recorded so you're done! The tool is a bit slow so don't be surprised if an operation takes ~10 s. The tool is backed by a cache so you won't see the results for ~2 hours. -- Michael

13 years, 10 months

Next week

by Andrew Stubbs

Hi Michael, I can't remember if I told you before, but I shall be away at the CodeSourcery (Ok, Mentor Graphics's ESD TOOLS) annual meeting most of next week. I ought to be back at work on Friday. In the meantime I shall be reading email, but not spending much time on Linaro work. I can probably still get the GCC release process done, but if you'd prefer Ramana did it this month then that's fine with me. Andrew

13 years, 10 months

Spinning the build

by Michael Hope

Hi Andrew. The current tip looks good. Could you please run the release process, spin the build, and fire it into the auto builders? Ta, -- Michael

13 years, 10 months

Backporting A15 changes

by Michael Hope

Hi there. Linaro is about what's next and, as part of this, we should backport any reasonable Cortex-A15 changes to our 4.6 branch. Richard and Matthew, could you let us know directly when new patches from ARM land upstream? We're already doing this but I thought I'd say it out loud. -- Michael

13 years, 10 months

Building Linaro GCC from source

by Javier Martinez Canillas

Hello, I'm trying to build the Linaro GCC from source on an x86_64 Fedora 16 box. I'm using as a guide a wiki entry I found in linaro.org site [1] that explains how to build a native version of the compiler. But instead of a native version I want to be able to cross-compile ARM binaries for my target machine. This is what I tried: [javier@munra src]$ wget -c http://launchpadlibrarian.net/86993387/gcc-linaro-4.6-2011.12.tar.bz2 [javier@munra src]$ tar xaf gcc-linaro-4.6-2011.12.tar.bz2 [javier@munra src]$ mkdir build && cd build [javier@munra build]$ ../gcc-linaro-4.6-2011.12/configure --target=arm-linux --disable-bootstrap --enable-languages=c --prefix=/home/javier/tools [javier@munra build]$ make -j4 && make install But got this error: make[2]: Leaving directory `/home/javier/src/build/gcc' Checking multilib configuration for libgcc... mkdir -p -- arm-linux/libgcc Configuring in arm-linux/libgcc configure: creating cache ./config.cache checking for --enable-version-specific-runtime-libs... no checking for a BSD-compatible install... /usr/bin/install -c checking for gawk... gawk checking build system type... x86_64-unknown-linux-gnu checking host system type... arm-unknown-linux-gnu checking for arm-linux-ar... arm-linux-ar checking for arm-linux-lipo... arm-linux-lipo checking for arm-linux-nm... /home/javier/src/build/./gcc/nm checking for arm-linux-ranlib... arm-linux-ranlib checking for arm-linux-strip... arm-linux-strip checking whether ln -s works... yes checking for arm-linux-gcc... /home/javier/src/build/./gcc/xgcc -B/home/javier/src/build/./gcc/ -B/home/javier/tools/arm-linux/bin/ -B/home/javier/tools/arm-linux/lib/ -isystem /home/javier/tools/arm-linux/include -isystem /home/javier/tools/arm-linux/sys-include checking for suffix of object files... configure: error: in `/home/javier/src/build/arm-linux/libgcc': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. make[1]: *** [configure-target-libgcc] Error 1 make[1]: Leaving directory `/home/javier/src/build' make: *** [all] Error 2 Before trying to compile I've installed the libgmp, libmpfr and arm cross tool-chain [2] Fedora packages so I guess all gcc dependencies are met (binutils, glibc, etc). Could someone be so kind to point me out what am I doing wrong? I'm sending as an attachment the config.log generated file. Please let me know if you need any more information about my setup and environment. [1]: https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative [2]: http://fedoraproject.org/wiki/Architectures/ARM/CrossToolchain Thanks a lot and best regards, Javier

13 years, 10 months

A high level try at KVM for ARM

by Michael Hope

I've taken a stab at the medium term requirements for KVM on ARM: https://wiki.linaro.org/WorkingGroups/ToolChain/Specs/KVMEpic I haven't looked outside Linaro so apologies if this overlaps with other people's plans. Peter, this is high level and hopefully matches what's in your head. I want to use this to do a project plan, see if it can be done in 6-9 calendar months, and see if we need more people. Are there any implementation details that we should call out, similar to calling out virtio and UEFI? Rusty, this should tell you more about where we're going. Mounir, you, Peter, and I should turn this into a basic project plan. -- Michael

13 years, 10 months

agenda for tomorrow's performance call.

by Ramana Radhakrishnan

Hi, Does anyone have anything they'd like to bring up in tomorrow's performance call. ? I don't have any topics other than following on action items from last time's call - which was comparing movw/ movt with constant pools . https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-01-10 Please add to it as you deem fit. cheers Ramana

13 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain January 2012