linaro-dev February 2016

linaro-dev@lists.linaro.org

11 participants
7 discussions

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

8 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

8 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/

8 years, 2 months

[ANN] patches.linaro.org upgrade

by Andy Doan

tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th around 16:00UTC. patches.l.o is being updated with a number of new improvements: * We are no longer a fork of the patchwork project and can stay up-to-date with improvements from the project. * Team memberships are now handled correctly. In the past moving to a new team meant we could either leave you in both teams and then show patch credits to both teams or remove you from the old team and have that team lose all contributions you made. * Multiple emails fixed. In the past doing Linaro work under another email (say @kernel.org) didn't properly contribute to patch metrics. This has been fixed (assuming you add your additional email account(s) to patches.l.o). * Performance - the new data layout is much more efficient resulting in faster page loads.

8 years, 2 months

gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux toolchain problem

by Aaron Gray

Hi, I have came back to getting a Linaro Jenkins local build working by pairing down the IFC6410 script. I have came to a point where the cross platform build tools are not working ! It does not look like the script installs them properly and I am confused as to wether the script actually installs them or whether it erroneously relies on them being present on the build machine ? I have attached my paired down .yaml script and the output build log. Either I am doing something wrong or the normal Qualcomms script does actually load the build tools. So either theres a bug to be fixed or I need to know how to install the build tools or both ! Many thanks in advance, Aaron

8 years, 2 months

Didn't see EBS with FlashBench

by Constantine

Hello, I couldn't figure out the Erase Block Size of my `Apacer Technology, Inc. Handy Steno 2.0/HT203` flash stick. As I understand, I have to run test as 1024 multiplied by factor of the stick capacity, is it? So, I ran tests with different blocksizes http://pastebin.com/Zb00RjfM Alas, I didn't see anything resembling EBS ☹ I could suppose it is either of 16384, 24576, 57344, but searching over the Internet shows that EBS never appears that low. Any ideas?

8 years, 2 months

[ANN] Gerrit upgraded to 2.11.5

by Paul Sokolovsky

Hello, All Linaro Gerrit servers have been upgraded to Gerrit 2.11.5 in planned manner. As was announced previously, we intended to upgrade directly to the latest 2.12, but literally couple of dates before upgrade we found out that there's known issue which affects replication services and thus our Git HA infrastructure. The bug has bean fixed by now in the Gerrit master, but the date of 2.12.1 release wasn't yet announced. As the aim of the current upgrade was to get on newer Gerrit version than now-old 2.10, we decided to upgrade to 2.11.5 in the meantime, and revisit upgrade to 2.12 after bug fix releases. Upgrade services appear to work stable based based on weekend monitoring, ditto for CI loops integrating with Gerrit. If you spot any issues, please provide details in a direct reply (not "Reply All") to this mail. One of the most user-facing changes in 2.11 is dropping support for "old" change screen UI design. About 20 people of (hundreds) in Linaro used the old design, and they were notified beforehand of the upgrade. You can read about changes and new features in 2.11 at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… As a sneak peek: * Yet in 2.10, there was introduced feature of editing a commit message in the Web UI. That's convenient if you e.g. spotted a typo in colleague's commit message - you don't need describe him/her an issue and make them rebase a change via command line, but can fix it on spot in the browser (subject to ACLs). * 2.11 brings this idea forward and allows to create entire patchsets via web browser, or post follow-up changes changes in the same way. It yet to be seen how useful this functionality is (in github, which has similar functionality, it's actually useful - if you e.g. read a README and spot a typo, you can submit a pull request with the fix on spot). Happy code reviewing from Systems Team! -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev February 2016