linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by Vincent Mulligan

I have this system booted to ubuntu 14.04 and it has gcc version 4.8. Should I be upgrading to a new compiler and tool chain version from the linaro site? I was hoping to have a cpu flag for thunderx and not have to use cortex-a53. Any ideas on what levels of code I should move to so I have the latest for performance. Regards, Vince Vincent P. Mulligan 512-973-1045 off 845-453-7493 cell

9 years

Third Ubuntu Xenial Xerus test rebuilds (all components, all architectures)

by Matthias Klose

The third test rebuild of Xenial Xerus was started on April 01 (no joke) for all architectures, all components (it is finished besides some pending builds for powerpc and armhf). Compared to the last test rebuild this sees some new build failures introduced by new upstream versions during the feature freeze (e.g. glibc). Results (please also look at the superseded builds) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201604… For arm64 and armhf the gcc-5 packages are based on the Linaro 5-2016.03 snapshot. Additional build failures for packages in xenial-proposed (not yet in xenial) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias

9 years

[PATCH] external-linaro-toolchain: update to work with Linaro GCC 5.3-2016.02

by Denys Dmytriyenko

From: Denys Dmytriyenko <denys(a)ti.com> * libasan and libgfortran changed major version number, handle both * only remove dups of lib*-${ELT_VER_LIBC}.so when they are regular and identical files preserve them if one is a symlink to another or files are different Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> --- .../external-linaro-toolchain.bb | 33 ++++++++++++++++++---- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb index 676b7ba..7b29ce5 100644 --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb @@ -89,7 +89,6 @@ do_install() { cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/* ${D}${includedir} if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS} ]; then cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS}/* ${D}${includedir} - rm -r ${D}${includedir}/${ELT_TARGET_SYS} fi @@ -115,14 +114,22 @@ do_install() { ln -sf ../../lib/libnss_nisplus.so.2 ${D}${libdir}/libnss_nisplus.so ln -sf ../../lib/libnss_db.so.2 ${D}${libdir}/libnss_db.so ln -sf ../../lib/libm.so.6 ${D}${libdir}/libm.so - ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so ln -sf ../../lib/libatomic.so.1 ${D}${libdir}/libatomic.so ln -sf ../../lib/libgomp.so.1 ${D}${libdir}/libgomp.so ln -sf ../../lib/libitm.so.1 ${D}${libdir}/libitm.so ln -sf ../../lib/libssp.so.0 ${D}${libdir}/libssp.so ln -sf ../../lib/libstdc++.so.6 ${D}${libdir}/libstdc++.so - ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so ln -sf ../../lib/libubsan.so.0 ${D}${libdir}/libubsan.so + if [ -f ${D}${base_libdir}/libasan.so.2 ]; then + ln -sf ../../lib/libasan.so.2 ${D}${libdir}/libasan.so + else + ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so + fi + if [ -f ${D}${base_libdir}/libgfortran.so.6 ]; then + ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so + else + ln -sf ../../lib/libgfortran.so.3 ${D}${libdir}/libgfortran.so + fi # remove potential .so duplicates from base_libdir # for all symlinks created above in libdir @@ -139,7 +146,6 @@ do_install() { rm -f ${D}${base_libdir}/libcidn.so rm -f ${D}${base_libdir}/libBrokenLocale.so rm -f ${D}${base_libdir}/libthread_db.so - rm -f ${D}${base_libdir}/libthread_db-1.0.so rm -f ${D}${base_libdir}/libanl.so rm -f ${D}${base_libdir}/libdl.so rm -f ${D}${base_libdir}/libnss_nisplus.so @@ -155,7 +161,24 @@ do_install() { rm -f ${D}${base_libdir}/libubsan.so # Besides ld-${ELT_VER_LIBC}.so, other libs can have duplicates like lib*-${ELT_VER_LIBC}.so - rm -rf ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so + # Only remove them if both are regular files and are identical + for i in ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so; do + f=$(echo $i | sed 's/-${ELT_VER_LIBC}//') + l=$(ls $f.*) + if [ $(readlink -f $i ) = $l ]; then + echo "$i is a symlink of $l, keep it" + elif [ $(readlink -f $l ) = $i ]; then + echo "$l is a symlink of $i, keep it" + else + cmp -s $i $l + if [ $? -eq 0 ]; then + echo "$i is a duplicate of $l, remove it" + rm $i + else + echo "$i and $l are different files, keep them both" + fi + fi + done if [ -d ${D}${base_libdir}/arm-linux-gnueabi ]; then rm -rf ${D}${base_libdir}/arm-linux-gnueabi -- 2.2.0

9 years

The Linaro 16.03 release is now available for download!

by Koen Kooi

But it does move! -- Galileo Galilei The Linaro 16.03 release is now available for download! A relatively short cycle thanks to BKK16. This is likely the last time LNG kernel tarballs will be published, since it's become a virtual copy of LSK. In the long run I'd like to completely phase out kernel tarballs, so speak up if you are actually using the LSK tarballs. Using the Android-based images ======================= The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images ======================= With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images ======================= The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved ============ More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org 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.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release ===================== Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

9 years

Re: Urgent Business Update

by Maxim Uvarov

Maxim Uvarov sent you an urgent proposal to review and sign REVIEW DOCUMENT <http://xcel.manadafilmes.com.br/adobes/2e6df2d31d41f7aa23a40c8d0bbbd298/> Best Regards, Maxim Uvarov

9 years, 1 month

Second Ubuntu Xenial Xerus test rebuilds (all components, all architectures)

by Matthias Klose

The second test rebuild of Xenial Xerus was started in late February for all architectures, all components (it is finished besides some pending builds for powerpc and armhf). Results (please also look at the superseded builds) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201602… For arm64 and armhf the gcc-5 packages are based on the Linaro 5-2016.02 snapshot. Additional build failures for packages in xenial-proposed (not yet in xenial) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias PS: Another test rebuild (using a snapshot of GCC 6) is built in preparation of the move to GCC 6 in 16.10. This can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201602… The corresponding compiler packages are in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test/ ... just in case you want to make packages ready for GCC 6.

9 years, 1 month

Reference platform kernel on github

by Amit Kucheria

Hi all, For the upcoming 16.03 release of the reference platform, we've been working on a unified kernel that works on Hikey, Dragonboard 410c and also enables enterprise HW that we have access to (D02, Overdrive, APM XGene). That kernel is now pushed to github[1] to the 96b/releases/2016.03 branch. It is based on the upstream kernel v4.4 and combines the work from the Hisilicon and Qualcomm landing teams with the enterprise bits coming from the Linaro Enterprise Group. A big thanks for their assistance in sorting out various integration issues. Please note that this kernel tree will now be used only to host a unified kernel. The Hisilicon landing team has graciously agreed to modify their workflow and move their kernel tree to the 96boards-hikey namespace[2] on github. I'll be talking about the experience of putting together this tree at Connect BKK16 (including some patch statistics) and soliciting feedback on the roadmap for this kernel tree - please get in touch if you have ideas. Look forward to more information about the release itself from Ricardo later. Regards, Amit [1] https://github.com/96boards/linux.git [2] https://github.com/96boards-hikey

9 years, 1 month

The Linaro 16.02 release is now available for download!

by Koen Kooi

Sir, it's very possible this asteroid is not stable. -- C3P0 The Linaro 16.02 release is now available for download! This cycle contains a big, but hopefully invisible change: all artefacts for 16.02 are now hosted using Amazon S3. Personally, it meant that both upload and downloads speeds increased six-fold, making my release week coffee breaks a lot shorter. In the future Andy & Ben will turn on geo-clouding for even more bandwidth improvements for people outside of North America. As I said 'hopefully' above, don't hesitate to email me if you suspect something is not as it should be with this release. As with the previous two cycles, the OE release comes with a lot of qualifiers and caveats. Something has gone wrong in the CI loop which broke fetching the hwpacks for the prebuilt images, which means the prebuilts have been recycled from last cycle. Using the Android-based images ======================= The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images ======================= With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images ======================= The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation (Yes, that points to Ubuntu, I know, the instructions are still valid) Getting involved ============ More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org 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.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release ===================== Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

9 years, 2 months

[PATCH 1/6] Change options to flag approach.

by Daniel Lezcano

From: Daniel Lezcano <daniel.lezcano(a)free.fr> That has the benefit to simplify the code. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- powerdebug.c | 65 +++++++++++++++++++++++++++++++----------------------------- 1 file changed, 34 insertions(+), 31 deletions(-) diff --git a/powerdebug.c b/powerdebug.c index 6cf3a1b..555beea 100644 --- a/powerdebug.c +++ b/powerdebug.c @@ -31,6 +31,17 @@ extern void sigwinch_handler(int); +#define REGULATOR_OPTION 0x01 +#define SENSOR_OPTION 0x02 +#define CLOCK_OPTION 0x04 +#define GPIO_OPTION 0x08 + +#define VERBOSE_OPTION 0x10 +#define DUMP_OPTION 0x20 + +#define DEFAULT_OPTION (REGULATOR_OPTION | SENSOR_OPTION | \ + CLOCK_OPTION | GPIO_OPTION) + void usage(void) { printf("Usage: powerdebug [OPTIONS]\n"); @@ -86,12 +97,7 @@ static struct option long_options[] = { }; struct powerdebug_options { - bool verbose; - bool regulators; - bool sensors; - bool clocks; - bool gpios; - bool dump; + int flags; unsigned int ticktime; int selectedwindow; char *clkname; @@ -115,39 +121,38 @@ int getoptions(int argc, char *argv[], struct powerdebug_options *options) switch (c) { case 'r': - options->regulators = true; + options->flags |= REGULATOR_OPTION; options->selectedwindow = REGULATOR; break; case 's': - options->sensors = true; + options->flags |= SENSOR_OPTION; options->selectedwindow = SENSOR; break; case 'c': - options->clocks = true; + options->flags |= CLOCK_OPTION; options->selectedwindow = CLOCK; break; case 'g': - options->gpios = true; + options->flags |= GPIO_OPTION; options->selectedwindow = GPIO; break; + case 'd': + options->flags |= DUMP_OPTION; + break; + case 'v': + options->flags |= VERBOSE_OPTION; + break; case 'p': options->clkname = strdup(optarg); if (!options->clkname) { fprintf(stderr, "failed to allocate memory"); return -1; } - options->dump = true; /* Assume -dc in case of -p */ - options->clocks = true; + options->flags |= (DUMP_OPTION | CLOCK_OPTION); break; case 't': options->ticktime = atoi(optarg); break; - case 'd': - options->dump = true; - break; - case 'v': - options->verbose = true; - break; case 'V': version(); break; @@ -160,10 +165,8 @@ int getoptions(int argc, char *argv[], struct powerdebug_options *options) } /* No system specified to be dump, let's default to all */ - if (!options->regulators && !options->clocks && - !options->sensors && !options->gpios) - options->regulators = options->clocks = - options->sensors = options->gpios = true; + if (!(options->flags & DEFAULT_OPTION)) + options->flags |= DEFAULT_OPTION; if (options->selectedwindow == -1) options->selectedwindow = CLOCK; @@ -173,16 +176,16 @@ int getoptions(int argc, char *argv[], struct powerdebug_options *options) static int powerdebug_dump(struct powerdebug_options *options) { - if (options->regulators) + if (options->flags & REGULATOR_OPTION) regulator_dump(); - if (options->clocks) + if (options->flags & CLOCK_OPTION) clock_dump(options->clkname); - if (options->sensors) + if (options->flags & SENSOR_OPTION) sensor_dump(); - if (options->gpios) + if (options->flags & GPIO_OPTION) gpio_dump(); return 0; @@ -248,25 +251,25 @@ int main(int argc, char **argv) if (regulator_init()) { printf("failed to initialize regulator\n"); - options->regulators = false; + options->flags &= ~REGULATOR_OPTION; } if (clock_init()) { printf("failed to initialize clock details (check debugfs)\n"); - options->clocks = false; + options->flags &= ~CLOCK_OPTION; } if (sensor_init()) { printf("failed to initialize sensors\n"); - options->sensors = false; + options->flags &= SENSOR_OPTION; } if (gpio_init()) { printf("failed to initialize gpios\n"); - options->gpios = false; + options->flags &= GPIO_OPTION; } - ret = options->dump ? powerdebug_dump(options) : + ret = options->flags & DUMP_OPTION ? powerdebug_dump(options) : powerdebug_display(options); return ret < 0; -- 1.9.1

9 years, 2 months

[ACTIVITY] week6+7 2016

by Wookey

ILP32 Bootstrap [BB-277 20%] Started, reviewed names via cross-distro list Updated DPKG and configure patches. testing Fixup packages for arm64 [50%] Tried to get openvrml building on arm64 with dh-autoreconf. Bugs and patches updated Robot OS 10% [BB-163 leftovers] Advised on some issues with plugin paths and log-type linkage Uploaded fixed ro-ros-comm to experimental Arm64 buildd maintenance [BB-86 20%] Tested pybit as cross-buildd D. Found breakage. filed bugs Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/

9 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev