| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
In patch of
"Fix: weston is not running after BSP 5.5 merged in cluster-demo",
I created common weston-init recipe for container guest.
This patch add image specific weston setting method.
Bug-AGL: SPEC-4099
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I0a47749932dc384e8a983b43214aefd939ccd06e
|
|
The recipe of wayland-ivi-extension has some issue.
1. GENIVI was rebrands as COVESA. As a resule, Github organization name
change to COVESA from GENIVI.
2. Original recipe has some error for recipe style.
3. Using http protocol at downloading.
This patch fix these issue.
Bug-AGL: SPEC-4096
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ic961ddecf7f2f30a024a4caef0c444391e493224
|
|
The weston with ivi-extention crash in no input device scene.
This patch add staging patch to wayland-ivi-extention to fix this issue.
Bug-AGL: SPEC-4096
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I8d3e6627c073213b2fe20df634889a19a730a4d5
|
|
The ivi guest for demo require wayland-ivi-extension on weston.
Current AGL is already removed it.
This patch import wayland-ivi-extension for weston-8 from meta-arago.
git://arago-project.org/git/meta-arago.git
Bug-AGL: SPEC-4096
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ib2c47e603334ae4ab590fdf48b8723956f73022b
|
|
weston is not running after BSP 5.5 merged.
This patch create new weston-init for gest usage.
Bug-AGL: SPEC-4131
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I9b6edc1c45aad0f985a307f3ffb0fe6a47195dd5
|
|
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
|
|
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
|
Naoto Yamaguchi
Scott Murray