Age | Commit message (Collapse) | Author | Files | Lines |
|
AGL IC integration use two display, one of the ivi, one of the cluster
in R-Car H3/M3 with Kingfisher environment.
This patch change cluster display from HDMI-A-1 to HDMI-A-2 only
a R-Car H3/M3 with Kingfisher environment.
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Idf1db5daba668e62a05bc7795da2e9d4a3e7e7cf
|
|
The bitbake recipe has style guide at
https://www.openembedded.org/wiki/Styleguide
Existing momiplay recipe does not fit this style guide.
This patch fix this issue.
Bug-AGL: SPEC-4094
Change-Id: Icb28faa991c8dd66807fcaadac77318c66dd77aa
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
|
|
The bitbake recipe has style guide at
https://www.openembedded.org/wiki/Styleguide
Existing mominavi recipe does not fit this style guide.
This patch fix this issue.
Bug-AGL: SPEC-4095
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I150ab671248be800c1d955c5e47a1792510ea4c7
|
|
When we want to use mapbox map drawing that use in mominavi,
we have to set App Key. This App Key need to get oneself
from mapbox developer site.
This patch add automatically App Key setting method.
How to do.
at local.conf/site.conf
MOMIMAP_MAPBOX_ACCESS_TOKEN = "mapbox App Key"
Bug-AGL: SPEC-4095
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Iaa87798b8794dd5bf409df2f3bf3a585fec506d8
|
|
The mominavi and momiplay have boot up issue such
as service dependency and environment variable.
This patch fix this issue.
Bug-AGL: SPEC-4099
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ia276c40e47a010bc2f93482aa0be5ce7416642d8
|
|
The momiplay is a mediaplayer example based on AGL sample app at CC release.
Existing agl-appfw is difficult to integrate into linux container guest,
because agl-appfw strongly depend SMACK label in host.
The mominavi is not require agl-appfw. It's temporally solution for MM release.
This patch import momiplay to create ivi guest for demo.
Bug-AGL: SPEC-4094
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ic0213f50ba570db56282d07b3f4f775664f05f78
|
|
The mominavi is a navigation example based on mapbox. It's based on
aglqtnavigation, that initial version of existing AGL demo navigation app.
Existing agl-appfw is difficult to integrate into linux container guest,
because agl-appfw strongly depend SMACK label in host.
The mominavi is not require agl-appfw.
It's temporally solution for MM release.
This patch import mominavi to create ivi guest for demo.
Bug-AGL: SPEC-4095
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ia84a291b6f9f50075a3dfe5e5dc2c6ff5bca4672
|
|
The ivi guest for demo use wayland-ivi-extension. That need to window manager.
This patch add tiny window manager for demo.
Bug-AGL: SPEC-4097
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I8392db39a7e2de5d8c61d511421afea9586d7922
|
|
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
|
|
The powervr firmware is including in gles-user-module in R-Car Gen3.
Typical container integration, gles-user-module only to installing in guest,
powervr kernel module only to installing in host.
In this case, powerver firemware is only to installing in guest,
but it is required by powervr kernel module.
This patch divide powervr firmware from gles-user-module, creating new package
gles-user-module-firmware. In addition, this patch add runtime dependency of
that firmware package to powervr kernel module.
Bug-AGL: SPEC-4130
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Ie8751bd618d076c9617870c367dacb3a9fdf1e7b
|
|
The lxc-host-image-demo can't build after BSP 5.5 merged.
Error message as a follow:
ERROR: Nothing PROVIDES 'linux-renesas' (but mc:agl-container-guest:
/../gstreamer1.0-plugins-bad_1.16.3.bb DEPENDS on or otherwise requires it)
linux-renesas was skipped: Set PREFERRED_PROVIDER_virtual/kernel to linux-renesas to enable it
Missing or unbuildable dependency chain was:
['cluster-refgui', 'qtmultimedia', 'gstreamer1.0-plugins-bad', 'linux-renesas']
ERROR: Required build target 'guest-image-cluster-demo' has no buildable providers.
Missing or unbuildable dependency chain was:
['guest-image-cluster-demo', 'cluster-refgui', 'qtmultimedia', 'gstreamer1.0-plugins-bad', 'linux-renesas']
This patch fix this build error.
Bug-AGL: SPEC-4129
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I0284a70aa38f855eb21e83e8c91e2df5a36cd7ef
|
|
Previously, libclusterapi and libclusteripc require to HACK in cross building time.
This issue was fixed by Hiroyuki Ishii at
https://gerrit.automotivelinux.org/gerrit/c/src/libcluster-ipc/+/26744
https://gerrit.automotivelinux.org/gerrit/c/src/libcluster-api/+/26745
This patch update revision to fixing point.
Bug-AGL: SPEC-4092
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I317db0612243c87530388eabf54e4fdd9c6abca0
|
|
When new container image add into lxc-host-image-demo, existing
image will not build.
In case of:
CONTAINER_IMAGES ?= "agl-container-cluster:guest-image-cluster-demo \
agl-container-ivi:guest-image-ivi-demo \
"
agl-container-ivi:guest-image-ivi-demo will be building,
but agl-container-cluster:guest-image-cluster-demo will not be building.
This patch fix issue for the build dependency creation to guests.
Bug-AGL: SPEC-4109
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I2ed6f91f0d4db90f337a6148d6630f85c1b5c97d
|
|
When I build lxc-host-image-demo, that out error message;
Nothing RPROVIDES 'lxc-config-cluster-demolxc-config-ivi-demo'
(but ~/meta-agl-devel/meta-agl-lxc/recipes-platform/images/
lxc-host-image-demo.bb RDEPENDS on or otherwise requires it)
The 'lxc-config-cluster-demolxc-config-ivi-demo' is must
describe to 'lxc-config-cluster-demo lxc-config-ivi-demo',
that need space between image name and image name.
This patch fix this issue.
Bug-AGL: SPEC-4109
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I3e3f057264c0e05872a1f04f9bf5c72af54115e1
|
|
AGL Instrument Cluster has common api library and framework.
This patch create package group for instrument cluster core packages.
Bug-AGL: SPEC-4092
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: Id9ec55dfc22cc7135f0973ef8a3421f8a614383d
|
|
The cluster api and ipc library was contributed by Nippon Seiki at SPEC-3952.
Original recipe of these was created by Tetsuro Komatsu from Panasonic.
https://github.com/agl-ic-eg/meta-agl/commit/476497689794ec37d5cbfd1f1797dfa060b0bd9b
This patch import these recipe from experimental repository.
Bug-AGL: SPEC-4092
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I25cb9773753e18621d2ee0e44f54ab9e9f1b4aaf
|
|
Cluster refgui upstreamd at SPEC-3942. But recipe was not changed.
Current refgui recipe has some issue.
* Referring to github repository now.
* Not changed recipe name from refgui to cluster-refgui.
* License description is old, that is already changed from MIT to Apach-2.0.
This patch fix these issue.
Bug-AGL: SPEC-4090
Signed-off-by: Naoto Yamaguchi <naoto.yamaguchi@aisin.co.jp>
Change-Id: I2742caf36ed50a2dbf41274d172a11be33708841
|
|
This is effectively a manual cherry-pick of commit:
37d3b1b316470fdcfebc59d5522bfbfefc025ff6
from the master branch with additional review and fixups.
The intent of these changes is to minimize the effort to backport
fixes from the master branch, which has been updated in preparation
for the switch to the next Yocto LTS release in early 2022.
Bug-AGL: SPEC-4144
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ic649d942ac043edc52976a3d4190590bb1c125e7
|
|
Add a bbclass that can be used to disable compilation in
module.bbclass based recipes, and dynamically activated bbappends for
the rcar3 kernel module recipes that use it and guest-build-specific
do_install overrides to get the userspace API headers installed
transparently to the userspace recipes. This avoids the complications
that would arise from using a full linux-renesas kernel build for
guest container images.
Bug-AGL: SPEC-4089
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I917e66ca024a2a507e615ba3a2a58c603a691142
(cherry picked from commit ed47409f52b66ef02de34916563de197955259b3)
|
|
To handle the Kingfisher supporting ULCB builds modifying the
IMAGE_LINK_NAME variable, add a MACHINE_SUFFIX variable that is
defined based on a new "kingfisher" feature being present in
AGL_FEATURES. Since so far only one platform has this issue,
this simple approach seems better than attempting to derive
the suffix from IMAGE_LINK_NAME using anonymous Python.
Bug-AGL: SPEC-4023
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ida769fbeb57208934f738dc5d1c867ab63c40bff
(cherry picked from commit aac67cb520cd945f960189d12ea9bbe1815891de)
|
|
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
|
|
With current integration of lxc-host-image-demo for rcar-gen3,
weston fails to start due to lack of gles modules so that demo
application doesn't come up. This change fixes it with adding
kernel-module-gles into lxc-host-image-demo image, only for
rcar-gen3 boards as of this moment (since lxc-host-image-demo is
maintained only for h3/m3 ulcb boards currently).
Signed-off-by: Hiroyuki Ishii <ishii.hiroyuki002@jp.panasonic.com>
Change-Id: I7874b125e6937c43bc706f63c971cb33d1a47a6c
|
|
Add a bbappend for packagegroup-core-tools-profile to disable the
LTTng related tools and perf when building for container guests to
avoid issues with kernel source dependencies.
Bug-AGL: SPEC-3983
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I394495bcc36505103066c62dd075edd1c5c360b0
|
|
Note that these changes do allow building and booting the
lxc-host-image-demo image, and the cluster-demo container does
get autostarted, but currently Weston fails to start in the
container.
Changes:
- Add a meta-rcar-gen3 dynamic layer with some bbappends to
disable problematic kernel module dependencies when building for
the container guest configuration. The ones used are based on
the ones in the IC EG container-bsp github repo, but fewer are
needed due to the use of linux-dummy, and the changes are done
via aglcontainerguest overrides.
- Add linux-renesas bbappend that disables the problematic default
addition of virtio.scc to KERNEL_FEATURES done in the
meta-virtualization layer, which currently is dependent on the
file coming from the linux-yocto kernel metadata, which is not
the case with linux-renesas. Upstream have been engaged on this
being a problem, so this may not be required in the future.
- Add lxc.scc to KERNEL_FEATURES in linux-renesas bbappend to
leverage the .cfg from meta-virtualization.
- Borrow a couple of tweaks from the IC EG container-bsp github
repo to disable firmware and disable the serial consoles in the
container guest build.
Bug-AGL: SPEC-3953
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I30fe6a940c5c44ee2ad71410a97a4495829c0b45
|
|
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
|