Stay updated with announcements or find answers to commonly asked questions. Submit a request or send us an email at email@example.com. Linaro - The future of Linux on ARM
Viswanath Puttagunta August 13, 2013 • Linaro FAQ's & Knowledgebase
Linaro Technical Support (LDTS) team is dedicated to support issues and questions associated with Linaro projects and monthly releases.
If you are unable to find the information you need, then you can open an LDTS ticket:
Please note that as a non-profit consortium, Linaro does not have a commercial product set; rather, we are Member funded for Member directed projects and efforts for Linux on ARM. LDTS gives priority to Member tickets and those tickets will be reviewed within 48 hours of submission by an LDTS Support Engineer. If you are from a Linaro Member company, please use your official email address when opening a ticket.
LDTS will work on community tickets on a best effort basis: If you are NOT from a Member Company, please be aware that your request will have a lower priority and will be worked on as time is available by the Support team. Because of this and in order to maximize your chances of getting quick responses to your queries please follow these advices:
To open a ticket to be viewed by our support team, you can send an email directly to firstname.lastname@example.org or
1. Click on “SUBMIT A REQUEST”
2. Your email address:
- Please sure to use your company email address especially if you are from a Linaro Member Company since we prioritize member company tickets over community tickets.
- Otherwise you can use any email address, although, we highly recommend you using your company email address even if you are not a Linaro Member.
- Enter the title of your request that best reflects the question or issue you are querying about.
4. For Description
- Enter a detailed description of the question or issue.
- When reporting an issue, please make sure you specify exact instructions of how to reproduce the issue.
5. Severity Level, Category Assigned
- Select the options that best fits the question or issue and the priority.
Linaro makes releases on a monthly basis, typically on the last Thursday of every month. The latest release information is always available at http://www.linaro.org/downloads/
The main contents of the release page are the following:
i. Linaro Engineering Builds (LEB)
ii. Linaro Stable Kernel (LSK)
iii. Linaro-GCC toolchain binaries
The rest of the contents on release page are used internally within Linaro. Refer to the corresponding working group’s home page for more information. Please stay tuned for LSK related information. Until we provide more information, refer to notes in http://www.linaro.org/downloads/#tab1 (Release Notes for release)
LEB is a full system build of popular open-source products that come with Linaro improvements pre-integrated.
These are the releases that the different working groups inside Linaro use to work on to add new features that are requested by Member Companies via their TSC (Technical Steering Committee) representatives. These new features that the working groups work on get fed back into the LEBs for every Linaro monthly release cycle. So, in summary, the primary audience of the LEBs are the Linaro working groups.
LEBs focus on integrating landing teams and working groups output; those are typically developed against the upstream trunk. Hence, you will find very recent/bleeding-edge kernel versions and other optimizations in user space in the LEBs.
If you need recent hardware enablement on an old kernel version for your product, the LEB is the wrong place to look for it.
The Builds & Baselines team in Linaro is responsible for the LEBs. They work with the different Linaro working groups (responsible for certain feature enablement/improvement) and the Landing team (responsible for the corresponding hardware platform) to make sure that all the different projects being fed into LEBs integrate properly without causing regression, and when they do cause some regression, work with them to resolve the issues before each Linaro Monthly Release.
LMB is a full system build of popular open-source products. LMBs are set up on specific request of a Linaro Core/Club Member company and the requirements or objectives for each LMB could be different based the corresponding Member Company objective.
The Linaro Builds & Baseline team initially helps with the Core/Club Member company in setting up the LMB, but it is really the responsibility of the Member Company Landing team to decide what features they want in the LMB, the frequency with which they want to make the releases and what testing needs to be done on the LMB.
Note that the Builds & Baseline team can push back on a particular LMB release, should the LMB release fail to meet very basic requirements of compile and boot. This is to avoid redundant support requests when we know that the release doesn’t work at all.
The target audience for the LMB depends on the specific Member Company objectives.
Refer to https://bugs.linaro.org/
Viswanath Puttagunta February 5, 2014 • Linaro FAQ's & Knowledgebase
The toolchain binary releases consist of: (http://releases.linaro.org/latest/components/toolchain/binaries)
2014.10 and later releases
Android cross-toolchain binaries are released separately (link to Android Toolchain question).
Our main focus is the following projects. We work directly with upstream communities: GCC, Binutils, GDB, glibc, LLVM, QEMU
The Linaro GCC project page is located at https://launchpad.net/gcc-linaro/
As mentioned in above project page, Linaro GCC is performance focused branch of the current GCC stable release and includes backports of the improvements and bug fixes that Linaro and others have done upstream. The project contains backports of work that we and the community have done to improve GCC on ARM.
Also, as Linaro is a not-for-profit company that works with open source, we work towards upstreaming the features we developed on linaro-gcc into mainline GNU GCC project.
ABE page: https://wiki.linaro.org/ABE
Victor Chong November 13, 2014 • Linaro FAQ's & Knowledgebase
OP-TEE is an Open Source TEE and is the result of collaboration work between STMicroelectronics and Linaro (Security Working Group). It contains the complete stack from normal world client API's (optee_client), the Linux kernel TEE driver (optee_linuxdriver) and the Trusted OS + the secure monitor (optee_os).
Please refer to the guide at https://github.com/OP-TEE/optee_os/blob/master/documentation/arm_trusted_firmware.md.
Yes, you can use QEMU or the Foundation Model (FVP) HW emulator.
Instructions are at https://github.com/OP-TEE/optee_os/tree/master/scripts.
Esla Anzaku February 24, 2014 • Linaro FAQ's & Knowledgebase
LAVA is an automated validation architecture primarily aimed at testing deployments of systems based around the Linux kernel on ARM devices, specifically ARMv7 and later.
By using the LAVA server at validation.linaro.org
If a member company wants to run automated tests on their platform(s) but does not want to install LAVA locally, The member talks to Linaro about this, sends their platform to Linaro LAVA engineers, it gets integrated into LAVA and becomes part of the Linaro LAVA lab at validation.linaro.org. Of Course, there is a mechanism within Linaro to grant access rights to the platform to any restricted group of individuals. Some member companies have done this already and their boards are managed by the LAVA lab at Cambridge. This allows the engineers in the member company to focus more on integrating their tests for LAVA to run. The QA team in Linaro is also willing to guide and help with tests integration if the need arises.
By installing LAVA locally
For some valid reasons, some member companies prefer not to send their boards to the Cambridge office, or send only a selected number, but want to use LAVA locally and have full control of it. Anyone can install a LAVA server and manage it as desired
There are two ways LAVA can be installed, depending on the how you intend to use it.
Here are the recommended steps to follow
We assume that you want to move your LAVA instance from Server-A to Server-B, and you have installed a LAVA instance on Server-B
WARNING: Information in the database of server-B would be lost.
The LAVA lab uses Salt to manage the LAVA master and LAVA workers' configurations. Please refer to https://docs.google.com/a/linaro.org/document/d/1ug4VtJ4sy8qsWcyy9s... for a summarized description of how this is done