The use of AGL UCB integration can be divided into two main categories.
- development platform for innovation, which means individual features and components, as well as prototyping and demo/PoC development
- It is preferable to reuse the existing AGL UCB (including the demo implementation), because the other will be developed from scratch and will not be available for some time.
- integrate reference system which is baseline of product embedded
- This will be a minimally configured system, which makes it very difficult to use for development purposes, such as new features and components.
Plan of K.K
Separate development platform and reference of product embedded
- Development platform
- Reusing agl-image-weston (because we need to use nested compositor architecture until DRM release manager will come)
- Introduce new layer to add-on container features on it
- add LXC support
- add container configuration for agl-ivi (for agl-demo-platform) and agl-ic (for agl-cluster-demo-platform)
- recipes and patches are common, identified by name, 'agl-ivi' and 'agl-ic' (default name, can be changed by variable in recipes/local.conf)
- network configuration
- use lxc-net by default (sharing host network adapter by containers to access internet)
- TBD: introduce guest pass-through (e.g. internet access permitted only to agl-ivi) and make these selectable
- very basic container manager
- To support nested compositor easily, add easy-launcher, lxc-launcher(runlxc)
- easy to select one from predefined configurations
- running 1 container, agl-ic or agl-iviivi (this is for using 'runqemu' which is not support multiple monitors)
- running 2 container, agl-ic and agl-ivi (this is for using host QEMU with display GTK, it can output multiple monitors)
Because multiple monitors cannot be usable on QEMU with AGL imageQEMU + SPICE can support multiple monitors but it requires spice-vdagent and xwayland(xserver + xrandr/Xinerama)not yet investigation: whether weston + xwayland can do the same above
- Reference of product embedded
- TBD