| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Goal is to reach a minimal meta-agl-core as base for IVI and IC work at the same time.
Trim dependencies and move most 'demo' related recipes to meta-agl-demo.
v2: changed to bbapend + .inc , added description
v3: testbuild of all images
v4: restore -test packagegroup and -qa images, compare manifests and adapt packagegroups.
v5: rebased
v6: merged meta-agl-distro into meta-agl-core,
due to dependency on meta-oe, moved -test packagegroup and -qa images
to own layer meta-agl-core-test
v7: Fixed comments from Paul Barker
v8: Update the markdown files
v9: restore wayland/weston/agl-compositor recipes/appends, reworked to
move app f/w specific changes to bbappends in meta-app-framework and
only demo specific weston-init changes to meta-agl-demo
v10: fix s/agldemo/aglcore/ missed in weston-init.bbappend
Description:
This patch is part 1 out of 2 large patches that implement the layer rework
discussed during the previous workshop. Essentially meta-agl-core is the
small but versatile new core layer of AGL serving as basis for
the work done by the IC and IVI EGs.
All demo related work is moved to meta-agl-demo in the 2nd patchset.
This should be applied together as atomic change.
The resulting meta-agl/* follows these guidelines:
- only bsp adaptations in meta-agl-bsp
- remove the agl-profile-* layers for simplicity
-- the packagegroup-agl(-profile)-graphical and so on
have been kept in meta-agl-demo
- meta-agl-profile-core is now meta-agl-core
- meta-agl-core does pass yocto-check-layer
-- therefore use the bbappend + conditional + .inc file
construct found in meta-virtualization
- meta-agl/meta-security has been merged into meta-agl/meta-app-framework
- meta-netboot does pass yocto-check-layer
- meta-pipewire does pass yocto-check-layer
Migration:
All packagegroups are preserved but they're now enabled by 'agl-demo'.
Bug-AGL: SPEC-3723
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: Ia6c6e5e6ce2b4ffa69ea94959cdc57c310ba7c53
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25769
|
|
Add a mechanism in the weston-init recipe to allow machine templates
to trigger installation of a systemd drop-in that adds a DRM device
dependency for the weston@.service unit. Also, tweak the qemux86-64
configuration to enable doing so against dev-dri-card0.device to avoid
startup failures due to the slow i915 initialization on e.g. the
UpSquared. This approach has been taken since it seems safer for now
to only apply it for qemux86-64 than doing a blanket default that
might then need to be over-ridden for vendor BSPs.
Bug-AGL: SPEC-3518
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I74ce4f878f9aa3f0d555f96a79578f3d8ca72550
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25675
ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
|
|
This makes the agl-compositor the default starting with Jumping Jellyfish
For development purposes, you have these variables at hand to influence the setup:
AGL_DEFAULT_WESTONSTART
AGL_DEFAULT_WM_SHELL
Check your conf/local.conf for details.
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
Change-Id: Iceb35375e04f947009800b80511f6360026403fe
|
|
Bug-AGL: SPEC-3374
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I1f3f78c8b15b1c488b12bff4fcc79c0511a48955
|
|
Update weston and weston-init bbappends to handle weston 6.0.0 to
7.0.0 upgrade and other upstream changes:
- weston 6.0.0 bbappend renamed for weston 7.0.0.
- Wildcard weston_%.bbappend removed, as none of its changes are
required with the latest upstream recipe.
- Update weston patches for 7.0.0. Notable changes are that the
patch to allow launching weston as a non-root user has been
reworked for the switch to meson for weston builds, and the
compositor backend patch for Waltham has been disabled until
someone more familiar with the code can update it.
- weston-init changes and udev rules updated to work with upstream
support for running weston as non-root. The major rework is to
simplify things such that all AGL configuration is done as an
over-ride to the new upstream weston@.service file. The ability
to specify which TTY to run weston on has been removed in favor
of upstream's hard-coded tty7 as part of this change, to cut down
on the amount of extra configuration required.
Bug-AGL: SPEC-2932
Change-Id: I6f8b213bacb2de7526aa1a3c01b1482be78becef
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
When the 'agl-compositor' distro feature is enabled, the AGL compositor
will be enabled and start at boot instead of Weston.
Change-Id: Idcd0c401c3d2c332637ddde1cd83d1fe85c4ae2a
Signed-off-by: Daniel Stone <daniels@collabora.com>
|
|
The recipe weston-init was setting smack labels of input devices
to ^. This had the effect to enforce processes that wanted to
read /dev/input/eventXX to have the Smack label System.
I changed the label to * and keep the protection of groups.
At the same time, a refactoring of the recipe make it cleaner to
maintain.
Bug-AGL: SPEC-2796
Change-Id: I3e2345d48a40b15254e68e25bbfcd9b22fcd8629
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Before that commit, the service weston was started as
user 'display' with a full setup of the user.
It means that all services normally started for user
started for weston: systemd-user, dbus, afm-user-daemon,
lightmediascanner (that is all at the moment). This is
useless and grabs resources.
This commit avoids to start a session for weston.
This saves resources. This changes is part of a set
of changes to run services as not root.
Bug-AGL: SPEC-545
Bug-AGL: SPEC-2492
Change-Id: If51d8fdf8c5e19d10151a2b96a79dc01bbb8ccb4
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
|
|
Rework towards agl profiles.
This change is part of a series of changes to create the
AGL profiles.
This set will mainly introduce the 'core' profile.
It is setup to be a drop-in change, thus some files were kept
in (dummy) locations for now.
However, they'll be taken care of in the next changes in this series.
The main target of the meta-agl-profile-core layer is to host:
- a minimal, bootable image with network and package management enabled
-- agl-image-boot
- a minimal image with network and packagemanagement and the AGL APIs
-- agl-image-minimal
The layer meta-agl-profile-graphical is used as superset of these
and includes support for egl+wayland+weston. All recipes concerning
graphics were moved there. This is not a full profile as we still have
to migrate some parts of meta-agl-demo in a follow-up changeset.
The roadmap as discussed during the F2F session in Karlsruhe is:
- week 16 : core profile and profiles w/o graphics
- week 17 : graphical profiles
- week 18 : final conversion of the demo image
v2: moved agl-login-manager from -graphics to -core (see Jose's comment)
v3: moved back after discussion - follow-up in separate changeset
Change-Id: Idacb0d1274baac1f63f8d1b850d4b1104ac33918
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
Jan-Simon Moeller
Scott Murray
Marius Vlad
Daniel Stone
José Bollo