.. # Copyright (c) 2024, Linaro. All rights reserved. # # This document is proprietary and confidential. # Unauthorized copying, distribution, or disclosure of this document or any part # of it is strictly prohibited without prior written consent from Linaro. # Terms, Definitions and Acronyms ############################### This document provides an overview of terminology used within Linaro. Some terms are industry-standard, while others are unique to Linaro. Each entry includes a brief explanation to support clearer understanding and effective use of Linaro assets. .. glossary:: ACS Arms `Architecture Compliance Suite `_ . A set of tests and specifications defined by Arm to ensure that hardware and firmware implementations comply with the Arm architecture requirements. The ACS typically includes tests for areas such as boot requirements, security, and runtime services, and is commonly used by silicon vendors and platform integrators to validate conformance. Assessment In the context of Linaro Remote Labs, this term is used in reference to the evaluation of a hardware platform (:term:`DUT`) to determine its ability to be automated and leveraged by the automation infrastructure. .cab Stands for `cabinet file` and is a compressed archive file. This is a packaging format originally defined by Microsoft and leveraged by :term:`LVFS` This is also the firmware input format for Linaro's ONELab Interoperability product. .cap: Stands for capsule update file as defined by UEFI specifications Capsule A UEFI Capsule is a firmware package that contains updates or configuration data, which can be securely processed and applied by the UEFI firmware during the system's boot process. It supports a standard method for firmware updates of various firmware components(images), such as system BIOS/UEFI, device firmware, or microcode. A UEFI Capsule contains: * **Metadata** including but not limited to version information, update instructions, and cryptographic signatures for security. * **Multiple(one to many) firmware images** or components are bundled together, allowing for complex updates in a single package. * **Guidance** for the UEFI firmware on how to apply the updates during the boot process. Compliance Run In regards to the ONELab Interoperability lab, a compliance run is the verification test of a predetermined :term:`Payload` against an instance of a customer built firmware used to validate interoperability between the two Device Type When using an LAA, the Device Type is the name for the DUT mounted on the LAA. Each embedded platform has a unique Device Type for configuation and tetst purposes. Device Under Test A customer platform being tested in the a LAVA instance or in Linaro Remote Labs DUT Abbreviation for :term:`Device Under Test`. EDK2 EFI Development Kit 2. This provides an alternate bootloader and tools to UBoot. Explore Boards The ONELab Explore Boards page is a publicly accessible page that shares interoperability results for any ONELab Platform where the user has publlished results to make them public. Firmware Release Stream In ONELab, this is A series of firmware images packaged in ONELab compatible .cab format that are grouped to execute on a Device Under Test that is seeking ONELab Interoperability compliance. A typical use is to add a new firmware to the series to be tested when a defect is corrected in that firmware. FOTA Firmware Over the Air. Associated with firmware updates. LAA Linaro Automation Appliance. See the `Overview `_ section of the LAA Users Guide Labs In most instances, the usage of this term within Linaro references remote / cloud-based integration, validation & tests instances that host customer platforms. LAVA Linaro Automated Validation Architecture LMS LAVA Managed Services. A proprietary Linaro technology used to support Embedded Integration, Validation, and Test. Coupled with the LAA, LMS provides a cloud-based, remote lab solution. LVFS `Linux Vendor Firmware Service `_. Coupled with the fwupd and other tooling to automate the secure upload of new firmware images to a target. Originally used for traditional PCs, now being leveraged by the embedded community as a standard way to package firmware updates. MIB Mechanical Interface Board. See the `Getting Started `_ section of the LAA Users Guide OTA Over-the-Air, typically associated with Over-the-Air software or firmware updates. Payload From UEFI perspective, also called an Image in the UEFI spec. Represents images encapsulated within a Capsule. Examples of images include UBoot, EDK2, TF-A, OP-TEE and other firmware components that may be built separately but packaged together as part of the overall firmware for a :term:`DUT`. From ONELab Perspective, refers to a test being executed to validate interoperability with a customer firmware under test. Payloads include various Linux Operating Systems, The Arm :term:ACS Test Suite, and participating company Applications. PCB Printed Circuit Board PARSEC `Platform AbstRaction for SECurity `_ Platform In the context of Linaro ONELab, a Platform is the combination of a DUT mounted on an LAA. PSA `Platform Security Architecture `_ TPM Trusted Platform Module UEFI `Unified Extensible Firmware Interface `_ specification. The firmware formatting standard required by Systemready. Chapters of particular interest: `Chapter 8.5.3.1 UpdateCapsule() `_ `Chapter 23 Firmware Update and Reporting `_ UEFI Shell The CLI that can be used to manually perform a capsule update among other things. WIC image A Yocto WIC image is a specialized type of disk image created by the Yocto Project's wic (OpenEmbedded Image Creator) utility. It's designed to be a complete, bootable image that can be directly written to a physical storage medium like an SD card, eMMC, or USB drive. Trivia: WIC stands for Open Embedded Image Creator. Insteardm of calling it "OEIC," WIC was selected, with W being the dipthong of OE. `Reference here `_