Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



h3ulcb
host

h3ulcb
Cluster-guest

h3ulcb
Cluster
Standalone
(TODO:)

Require
QM

container-bspmeta-rcar-gen3-hostx--yeshost extension for meta-rcar-gen3
meta-rcar-gen3-guest

-

x-yesguest extension for meta-rcar-gen3
meta-renesasmeta-rcar-gen3xxxnosupport for Renesas Electronics's platforms
meta-aglmeta-agl-bspxxxno

agl specific board support
*. This layer is shared by both agl ivi and agl cluster.  When this layer modify to update for ivi use case, it propagate to agl cluster. This point is serious issue, but I don't have good idea without "agl cluster doesn't use meta-agl and meta-agl-bsp".

meta-agl-corexxxyes

agl core software stack layer
Reduced from existing meta-agl-core

meta-agl-core-test---no
meta-agl-hostx--yesSoftware stack layer for AGL containerization host
meta-agl-ic-xxyescommon software stack layer for ic eg
Software stack layer for Instrument Cluster (without IVI based existing Instrument Cluster) 
meta-agl-ivi---no

common software stack layer for ivi-pr eg
Software stack layer for IVI (with IVI based existing Instrument Cluster)

meta-app-framework---no
meta-netboot---no
meta-pipewirex--noMore detail, depends on audio management work.
meta-agl-develmeta-agl-drm-leasexx-yes
meta-agl-jailhouse---no
meta-egvirt---no
meta-oem-production-readiness---no
meta-speech-framework---no
meta-agl-qmxxxyesIncluding assessment data for a part of poky and meta-oe.
meta-agl-demo-cluster-xxnoDemo layer for Instrument Cluster (without IVI based existing Instrument Cluster) 
meta-agl-demo---noagl demo software layer
poky

metaxxxno
meta-pokyxxxno
meta-poky-bspxxxnoWill be remove
...---no
meta-openembeddedmeta-oexxxno
meta-pythonxxxno
...---no

...

            Current IC layer structure don't have 'bsp' and 'external' directory. It will change.

            Currently, should separate IC demo and IVI based demo.  Because existing meta-agl-demo fully depend to meta-app-framework.
            We will develop security mechanism for embedded containerized platform, but it is not current work.  1st step is a un-privilege gest.  We can't import SMACK.


BSP Issue

Issue for current AGL design.

Image Added


Idea 1:  Heavy maintenance

Image Added


Idea 2:  Best solution, but how to do?

Image Added


Which recipe should move into meta-agl-ivi?

meta-agl$ grep SUMMARY -R meta-agl-core/*

recipeSUMMARYShould beWhy
meta-agl-core/recipes-connectivity/connman-ncurses/connman-ncurses_git.bbSUMMARY = "A simple ncurses interface for connman"meta-agl-iviThis OSS will assess?? May not.
meta-agl-core/recipes-graphics/wayland/weston-ini-conf.bbSUMMARY = "Configuration file for the Weston and AGL Wayland compositors"meta-agl-coreNot specific IVI
meta-agl-core/recipes-graphics/wayland/agl-shell-activator_git.bbSUMMARY = " Application that switches/activates other application's windows "TODONo detaile
meta-agl-core/recipes-graphics/wayland/agl-compositor_git.bbSUMMARY = "Reference Wayland compositor for AGL"meta-agl-coreNot specific IVI
meta-agl-core/recipes-graphics/rba/librba_1.0.bb:SUMMARY = "RBA"meta-agl-coreNot specific IVI
meta-agl-core/recipes-graphics/rba/rba-config.bbSUMMARY = "Rule Based Arbitrator Model required for RBA policy compositor."meta-agl-core
meta-agl-core/recipes-platform/images/agl-image-boot.bbSUMMARY = "An AGL small image just capable of allowing a device to boot."meta-agl-core
meta-agl-core/recipes-platform/images/agl-image-core-autobuilder.bbSUMMARY = "A very basic Wayland image with a terminal"meta-agl-iviDepend to IVI specific package groups
meta-agl-core/recipes-platform/images/agl-image-weston.bbSUMMARY = "A very basic Wayland image with a terminal"meta-agl-iviDepend to IVI specific package groups
meta-agl-core/recipes-platform/images/agl-image-minimal-crosssdk.bbSUMMARY = "Cross SDK of Full AGL Distribution for core profile"meta-agl-core
meta-agl-core/recipes-platform/images/agl-image-minimal.bbSUMMARY = "An AGL small image just capable of allowing a device to boot."meta-agl-core
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-devel.bbSUMMARY = "Provides a set of tools for development for AGL DISTRO"meta-agl-core
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-graphical-multimedia.bbSUMMARY = "The software for application framework of AGL IVI profile"meta-agl-iviDefined for IVI specific package groups. Not common.
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-profile-graphical.bbSUMMARY = "The middleware for AGL IVI profile"meta-agl-iviDefined for IVI specific package groups. Not common.
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-os-commonlibs.bbSUMMARY = "The packages of middlewares for AGL IVI profile"meta-agl-iviDefined for IVI specific package groups. Not common.
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-boot.bbSUMMARY = "Minimal boot requirements"meta-agl-core
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-security.bbSUMMARY = "The packages of middlewares for AGL IVI profile"meta-agl-iviDefined for IVI specific package groups. Not common.


find meta-agl-core -name *.bb*
meta-agl-core/recipes-kernel/linux/kernel-devsrc.bbappend
meta-agl-core/recipes-platform/images/agl-image-boot.bb
meta-agl-core/recipes-platform/images/agl-image-core-autobuilder.bb
meta-agl-core/recipes-platform/images/agl-image-weston.bb
meta-agl-core/recipes-platform/images/agl-image-minimal-crosssdk.bb
meta-agl-core/recipes-platform/images/agl-image-minimal.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-image-boot.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-image-minimal.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-devel.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-graphical-multimedia.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-profile-graphical.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-graphical-weston.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-connectivity.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-os-commonlibs.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-boot.bb
meta-agl-core/recipes-platform/packagegroups/packagegroup-agl-core-security.bb
meta-agl-core/classes/image_types_wic_workaround.bbclass
meta-agl-core/classes/sanity-meta-agl-core.bbclass
meta-agl-core/classes/cloc.bbclass
meta-agl-core/recipes-core/systemd/systemd-conf_%.bbappend
meta-agl-core/recipes-core/systemd/systemd_%.bbappend
meta-agl-core/recipes-devtools/gdb/gdb_%.bbappend
meta-agl-core/recipes-devtools/cmake/cmake_%.bbappend
meta-agl-core/recipes-graphics/wayland/waltham_%.bbappend
meta-agl-core/recipes-graphics/wayland/waltham_git.bb
meta-agl-core/recipes-graphics/wayland/weston-ini-conf.bb
meta-agl-core/recipes-graphics/wayland/weston-init.bbappend
meta-agl-core/recipes-graphics/wayland/weston-ini-conf.bbappend
meta-agl-core/recipes-graphics/wayland/agl-shell-activator_git.bb
meta-agl-core/recipes-graphics/wayland/waltham-transmitter-plugin.bb
meta-agl-core/recipes-graphics/wayland/weston_8.0.%.bbappend
meta-agl-core/recipes-graphics/rba/librba_1.0.bb
meta-agl-core/recipes-connectivity/connman/connman_%.bbappend
meta-agl-core/recipes-connectivity/busybox/busybox_%.bbappend
meta-agl-core/recipes-support/ptest-runner/ptest-runner_2.%.bbappend
meta-agl-core/recipes-extended/gperf/gperf_%.bbappend


How to understand distribution structure?