| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Since there is some race condition between initialization of
drm-lease-manager and startup of lxc guest images in
lxc-host-image-demo currently, we sometimes observe a startup
failure of the cluster-guest, especially on refhw platform,
due to delay of lease device creation.
This change adds unit dependencies between lxc and
drm-lease-manager so that lxc guests can be started after lease
devices creation stably.
Bug-AGL: SPEC-4427
Signed-off-by: Hiroyuki Ishii <ishii.hiroyuki002@jp.panasonic.com>
Change-Id: I16183c784d8e1132ba316f842e5dedc664ec2853
|
|
Previously, weston.service is using environment specific setting,
it propagated from bind mounted host side config file.
.
This patch remove this propagation. After this patch,
these setting bring to lxc config files.
Bug-AGL: SPEC-4370
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I4f73a8ca08e149a82648ac5fcdf647c97edc2429
|
|
When weston is running in guset, it can't find input device.
It cause by udev data dependency for libinput.
IC EG member investigate some input support plan now,
but it require to long way.
This patch is workaround for next release to support input
device in ivi-demo guest. That based on CES2020 demo method.
Bug-AGL: SPEC-4136
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I622a53add8441374d3c3be6e905f46ee56d51dad
|
|
Existing lxc config creation recipe is supporting two type string
replacing. The network interface setting has required to multi line
replacing at aec683913cd645fcf18d7633a12a7b4b42215f69.
These flexibility will support by container manager that is under
developing. But we need quick solution for that now.
This patch provide quick solution. This patch support any network
interface usage in guest.
Bug-AGL: SPEC-4132
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I5da97492610124ddfe050660e0cc2c2c5559d5b9
|
|
Currently IVI guest doesn't start automatically.
IVI guest shall not start in single display environment.
IVI guest shall start in dual display environment such as kingfisher.
This patch add automatic start support for IVI guest in dual
display environment.
Bug-AGL : SPEC-4135
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Idcb8c7961f7d2e7f4bf77f1fb81065d16ed124a2
|
|
In ivi guest, must require to internet connections.
This patch enable network connection in ivi guest.
Detaille:
Bind eth0 device to ivi guest.
Enable systemd-networkd to manage network connection.
Add network interface setting to set IP address using dhcp.
Bug-AGL: SPEC-4132
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Icf0fb386d1efafb060a66e0cab727f93d5e8e7fd
|
|
AGL IC integration will have two guests, one of the cluster demo,
one of the simple ivi demo.
This patch add initial support for ivi container for demo.
Bug-AGL: SPEC-4099
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I4a1da6e30aee99e8ce2e2c404da78a413c647fd2
|
|
This is mostly the result of running a slightly customized version
of the convert-overrides.py script from poky with additional
overrides added. A few minor fixups were done by hand afterwards
during a review of the changes.
The intent of these changes is to minimize the effort to keep the
"next" branch that builds against poky master up to date and tested
in preparation for the switch to the next Yocto LTS release in
early 2022.
Bug-AGL: SPEC-4052
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I0bbae97331abee1367b368ce54ab39e3162a12ec
|
|
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
|
|
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
|
Hiroyuki Ishii
Naoto Yamaguchi
Scott Murray
George Kiagiadakis