Skip to content
Snippets Groups Projects
Select Git revision
  • 87adbb1579b0689caeba15ff6217c77f1841b92d
  • master default protected
  • wip/wlozano/repo-configuration
  • wip/em/http-redirects
  • wip/Q1_release_schedule_fix
  • wip/daissi/T8768-policy-for-statically-linked
  • wip/daissi/add-pw-wp-presentations
  • wip/martyn/T8303-Documentation-CI
  • wip/T10461
  • wip/martyn/T8303-doc-validation
  • wip/test_url
  • wip/martyn/T9765-developer-guide-v2024
  • wip/cdan1kor/devroot
  • wip/rfw_LAVA_doc_update
  • wip/q3_sch_fix
  • allowbuilldep-star
  • wip/sagar/agl-compositor
  • wip/sagar/agl-compositor-test
  • wip/wlozano/release-flow-rework
  • wip/obbardc/device_roc-rk3399-pc
  • wip/adalessandro/amd64-switch-to-upsquared
21 results

hwpackforvendors.md

Blame
  • Martyn Welch's avatar
    Martyn Welch authored
    The wiki is now locked and a final dump of data performed. Update the site
    to reflect these latest changes, including adding back a piece of ascii
    art removed in the last dump as it was confusing the conversion tool.
    
    Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
    cc285458
    History
    date = "2019-11-25"
    weight = 100
    
    title = "User:Peter HWPACKforVendors"
    
    aliases = [
        "/old-wiki/User:Peter/HWPACKforVendors"
    ]

    Apertis hwpack: requirements for vendors

    This is the output of APERTIS-6608.

    Introduction

    Adding support to a new architecture, or to a new board is done trough cycles of hardware bring-up. During each cycle, the developer enables new features, or fixes known issues until the hardware support is considered adequate. On a low level perspective, hardware bring-up is about developing and adjusting a few components such as the boot loader and the kernel to provide the hardware initialization and hardware support for the operating system. When using Apertis, the output of the hardware bring-up will be the hwpack, which is a platform specific collection of artifacts that are needed for the hardware initialization and support.

    Debos is the main tool used for building Apertis images. Debos allows for modular design of images, and is capable of creating the modules and the images. The image modules used by Apertis are:

    * hwpack: platform-specific artifacts related to hardware initialization and hardware support * ospack: platform-independent artifacts common to a set of images such as target or development images

    The apertis-image-recipes is the code repository that hosts the Debos recipes that are used for creating Apertis images. While the ospack recipes are explicitly named, the hwpacks are defined inside the apertis-image-*.yaml files. The rationale is that the hwpack is a set of steps and components that extends the ospack to boot on the target. Looking at the apertis-image-uboot.yaml recipe, we see that Debos uncompress the ospack to add changes on top of it, that it creates the image with partition scheme, filesystems, u-boot, and that it deploys the modified ospack into the image adding hwpack artifacts such as the kernel, and other system packages.

    Apertis is both a platform and the automated infrastructure that is used to conveniently evolve and cheaply maintain the platform. The infrastructure uses automation to ensure quality and minimize maintenance costs. Some of the hwpack requirements and suggestions are in place to avoid deviation from the existing Apertis processes.

    Requirements

    Source code

    Long term support

    Updates

    Security fixes

    Boot loader

    Kernel

    Suggestions

    Boot loader

    Kernel

    Example of Apertis hwpack

    Final words