summaryrefslogtreecommitdiffstats
path: root/templates/feature/agl-lxc
AgeCommit message (Collapse)AuthorFilesLines
2021-07-30meta-agl-lxc: integrate pipewire-ic-ipc and pull in agl-pipewireGeorge Kiagiadakis1-1/+1
pipewire-ic-ipc offers a small unix socket server that listens for the SUSPEND & RESUME requests from its clients and sets the "suspend.playback" metadata on pipewire. This allows wireplumber instances to catch changes to this metadata property and suspend or resume playback from applications appropriately. The purpose of this is to allow Instrument Cluster applications to suspend audio from other containers and play certain sounds exclusively. The server-side is implemented as a pipewire module that gets loaded in a separate pipewire process and behaves as a client to the actual pipewire daemon. It is not affected by pipewire daemon's stops & reloads, as it re-connects automatically to pipewire and synchronizes the "suspend.playback" status. The icipc-client application is an example that is not meant to be used in production. IC applications are expected to use the library directly. It is provided for testing & demo purposes. v2: - removed the client from the host image - updated the pipewire-ic-ipc git URI to point to AGL's gerrit Bug-AGL: SPEC-4027 Signed-off-by: George Kiagiadakis <george.kiagiadakis@collabora.com> Change-Id: I9e326797ce899c2579a0d7794202091e455c6c98
2021-07-13Drop agl-virt dependencyNaoto Yamaguchi3-5/+11
The agl-lxc depend to only lxc from meta-virtualization. On the other hand, current setting depend to agl-virt to import meta-virtualization. In this case, the change of agl-virt propagate to agl-lxc, it's broken to quality assessment software stack. This patch drop to agl-virt dependency. Bug-AGL: SPEC-4014 Signed-off-by: Naoto Yamaguchi <i33399_yamaguchi@aisin-aw.co.jp> Change-Id: I7863a00576ead96b33428907a67c0ab6af33358c
2021-06-29meta-agl-lxc: Update host kernel configurationmarlin_12.90.0marlin/12.90.012.90.0Scott Murray1-0/+6
Add a generic kernel bbappend and associated conditional include file that uses the new AGL_KCONFIG_FRAGMENTS to disable all other AGL provided kernel configuration, replacing it with a local fragment to enable minimal required features for LXC support. The previous linux-renesas bbappend to leverage the meta-virtualization provided kernel configuration has been removed, and the agl-lxc template has been updated to drop the "virtualization" distro feature (thus disabling all meta-virtualization additions). Bug-AGL: SPEC-3983 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: Iea91c3e273fe01d764adb644efc212f92e4a92fe
2021-06-07Add meta-agl-lxcScott Murray4-0/+20
Add meta-agl-lxc layer with LXC container integration recipes, and "agl-lxc" feature to enable its use. The changes are based on the previous prototypes by Tadao Tanikawa and the updates done for the trial integration layers on the agl-ic-eg github by Naoto Yamaguchi, Hiroyuki Ishii, and Jan-Simon Moeller. The layer can be used by running aglsetup.sh with just the "agl-lxc" feature, then building lxc-host-image-demo with bitbake. Notes: - The agl-lxc feature enables a "agl-container-guest" multiconfig configuration for building the guest image(s). This suffices for demonstrating integrated builds with multiconfig, but may change in the future with extension of aglsetup.sh to add more flexibility. - There are guest-image-minimal and guest-image-cluster-demo recipes that are intended as a base container template and a demo of its use. The cluster-demo image contains the demo cluster reference UI application, and is roughly equivalent to what is named cluster-guest in the agl-ic-eg trial integration configuration. - There are likewise lxc-host-image-minimal and lxc-host-image-demo images. The host demo is configured to pull in the cluster-demo guest image, and configuration has been added such that it will automatically boot and start the cluster reference UI application. - Unlike previous work where the guest container image is added to the host image via a recipe that packages up the guest image's contents, a more direct scheme is used where the guest image is unpacked inside the host image rootfs via the use of the ROOTFS_POSTPROCESS_COMMAND mechanism. This avoids some hassles around potentially mismatched user and group id lists in the host and guest images, with the additional benefit of being faster. However, using this scheme is to some degree only necessary due to the use of LXC with unpacked guest image hierarchies. With other container tooling that uses e.g. OCI images, a revert to using packages may be preferable. - The reusable logic in the lxc-host-image-minimal recipe makes some assumptions wrt naming. They are: - guest image names have the format guest-image-<name> - guest images have a corresponding LXC configuration file recipe with the name lxc-config-<name> The intent is to simplify reuse of the base minimal recipes, but this can be reworked if deemed too restrictive. - packagegroups for e.g. pipewire and weston have purposefully not been defined at this time. It seems better to wait until it is more obvious how useful they would be. Limitations: - The host image is currently rebuilt every time to work around an issue with multiconfig dependencies that is being investigated upstream. This can hopefully be removed in the near future. - The demo images are currently in meta-agl-lxc for convenience. It may make more sense for them to reside in another location to ease shifting some things into meta-agl. - At the moment, only qemux86-64 has been tested. The changes to enable host and guest configuration tweaks for the rcar3 BSP need further investigation and discussion on where they should be maintained. Bug-AGL: SPEC-3953, SPEC-3955 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: I69d41f1d1c736f05cf3b4997dbda147879e2e25d