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.


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