User Tools

Site Tools


agl-distro

AGL Distribution

AGL is creating an automotive specific Linux distribution that unifies the software that has been written in a number of places already, such as GENIVI and Tizen IVI.

The code is maintained and published at the AGL project git repositories.

Issue tracking and work planning for the AGL Distribution Project is done in Jira at https://jira.automotivelinux.org.

You can download software for the following hardware Download and build

Release notes for current and past releases can be found here

Supported Hardware

AGL makes two types of hardware support available: Reference BSPs and Community BSPs.

1) Reference Boards have Board Support Packages (BSPs) that are maintained by their sponsoring companies and are included in our Jenkins CI system. Reference BSPs have snapshot builds that are made available daily and are fully validated with test results made available for every major AGL release.

2) Community Boards have BSPs that are maintained as a best effort by the AGL community based on upstream BSPs. Community Boards include some of the most-used Hobbyist boards such as the Raspberry PI or older automotive boards.

Reference BSPs

Board Name SOC Quick Start Guide Snapshot Snapshot Binary Chinook 3.0.2 src tar Chinook 3.0.2 Binary
Reneses Porter Renesas R-Car M2 Porter Quick Start Porter Snapshot Note 1 agl-chinook-3.0.2.tar.bz2 n/a (see Note 1)
QEMU x86 (64 bit) tbd qemux86-64 vmdk file (see Note 2) agl-chinook-3.0.2.tar.bz2 agl-demo-platform-qemux86-64.vmdk (see Note 2)
Intel Minnowboard Max Atom E38xx Intel Quick Start intel-corei7-64 Snapshot agl-demo-platform-intel-corei7-64.hddimg agl-chinook-3.0.2.tar.bz2 agl-demo-platform-intel-corei7-64.hddimg

Note 1: A minimum build for the Porter board is available as a snapshot which does not include the graphics libraries. A full Porter binary is unavailable due to Renesas License restrictions on the graphics driver. Please see Quick Start guide for instructions to build your own image.

Note 2: VirtualBox / Vmware users can use the provided vmdk and import it. Be aware that you have to comment-out a line in /etc/xdg/weston/weston.ini to look like: #backend=drm-backend.so

Community BSPs

Board Name SOC Build Instructions Snapshot Builds Snapshot Binary
Vayu EVM TI Jacinto 6 TI Vayu
NXP Wandboard NXP i.MX6
NXP SABRE NXP i.MX6 Sabre Lite
DragonBoard
Raspberry PI 2/3 Broadcomm 2836 Building AGL for Raspberry Pi raspberrypi3 agl-demo-platform-raspberrypi3.rootfs.rpi-sdimg-ota

Subsystems and Maintainers

The AGL Software Architecture was deconstructed to determine where there are synergies or vertical architecture slices that can be managed as part of the larger distribution. This is shown in the diagram below. For each of those subsystems there is a subsystem maintainer. In some cases there is a subsystem architect as well.

Governance

The roles within the AGL development team include Architect and Developers. Developers are identified as either Contributors (or Committers) or Mergers (Maintainers). Among the Maintainers the AGL Distribution has a group of overall maintainers and subsystem maintainers.

Architect

There System Architects and Subsystem Architects on the AGL project. Within their sphere and expertise both types of architects have similar responsibilities.

  • Requirements analysis for the subsystem as documented in the requirements management database or other informal mechanisms as required.
  • Architecture of the subsystem including package selection and configuration related packages in the subsystem.
  • Keeping current with upstream code releases, roadmaps, and patches
  • Create and maintain the subsystem level API that is published for developers.
  • Subsystem architects may be responsible for the possible further breakdown into sub-subsystems.

Developers

Developer roles are defined on this page

Subteam Pages

Demo Apps

FIXME - add description of process for developing the apps.

agl-distro.txt · Last modified: 2017/03/10 21:57 by waltminer