| Age | Commit message (Collapse) | Author |
|---|
|
This ports the 4.14 kernel recipes from upstream sumo branch into
meta-amd to start with.
User should be able to build an image for a BSP on which 4.14 kernel
was supported previously.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds LAYERSERIES_COMPAT warrior to common and all BSP layers, i.e.
* common
* v1000
* r1000
* snowyowl
* amdfalconx86
* steppeeagle
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes a patch that was backported from upstream which is already
a part of the source code of systemd v241 that we are using in warrior
branch.
Associated commit in systemd git repo (branch: v241-stable):
cde942f61bf231ea4a0d50780cdb4e744458daeb
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades libdrm from v2.4.96 to v2.4.97 according to
yocto warrior branch recipes.
This also eliminates a circular dependency:
libdrm -> cairo -> mesa -> libdrm
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades mesa from v19.0.0+git to v19.0.1 according to
yocto warrior branch recipes.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades llvm from v7 to v8.0.0 according to yocto warrior
branch recipes.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades gstreamer1.0-omx from v1.12.% to v1.14.4 according to
yocto warrior branch recipes.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Xorg upstream have replaced the individual xorg proto repositories
with one master repository.
This moves xf86-video-amd xorg-driver to the new system.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Xorg upstream have replaced the individual xorg proto repositories
with one master repository. This moves libvdpau to the new system.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades vaapi components:
* libva
* libva-x11
* libva-utils
from v2.1.0 to v2.4.0 according to yocto warrior branch recipes.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes inclusion of firmware-wireless pkg which is required in
mentor's mel/mel-lite distros.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes a workaround for a mentor's mel related issue that is no longer
applicable.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor iot packagegroups setting as required by the
mel-iot layer that is no longer supported for AMD BSPs.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the condition that multimedia & networking pkgs should
only be included when mentor distro mel is being built.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Mentor's mel/mel-lite distros have EXTRA_IMAGE_FEATURES i.e. "graphics"
and "multimedia" which control the inclusion of our AMD BSP specific
features i.e. "amd-feature-graphics" and "amd-feature-multimedia".
This removes mentor specific "graphics" & "multimedia" feature configs
such that now we leave our AMD BSP specific features to be enabled by
the machines themselves in their corresponding conf/machine/<bsp>.conf
files. But the feature packages will be enabled conditionally in the
amd-features.inc file depending on the availability of "x11-base" in
the IMAGE_FEATURES for graphics pkgs and "alsa" in COMBINED_FEATURES
for the multimedia pkgs.
Also, MEL structure required "x11" in MACHINE_FEATURES for targets that
required X11/GUI based images otherwise x11 is dropped from the distro.
This also removes that config as x11 is not actually a machine feature.
See following commits for background:
2dd6c485fda57ef86ce7d48536ca4d0b42cebd3e
5d05eb929bb27c30325471c6f01812ec0f125c72
63cbf8208d70f49fe46f3e938df3ee04455b7fed
fca5be162809ffc1c3615dc629ada323a5aeb51a
36b85e0aec98955257826598e43bc9b81d75fc9f
7f28a188039e29455d5f58213cd3fc875412c4bc
8c46b32fb1225fe5aa015be0c958ff97ec2d7e56
We are doing this in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor mel specific tools-testapps configs in
preparation for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor mel specific tools-profile configs in
preparation for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes mentor mel distro specific sato GUI config bits in
preparation for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes a mentor specific mini-x-session display resolution
setting where mini-x-session sets the display resolution to 1024x768
by default by invoking xrandr, whereas we wanted the system to make use
of all the available resolution on the 4k displays.
This isn't applicable anymore, therefore removing it in preparation for
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor installer support bits (related to intent
of not deploying ISO images to the installer) in preparation for
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes mentor docker support bits in preparation for
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor security selinux support bits in preparation
for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor mel-lite distro specific codebench gcc8
support bits in preparation for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor qt5 support bits in preparation for the
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor swupdate bits in preparation for the
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Move changes from meta-r1000 to common
|
|
This allows usage of the mesa upgrade on BSPs other
than the r1000 as well.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This allows the latest updates to be used on other BSPs
such as the v1000 where these modifications are applicable.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This removes the older DPDK v18.02.2 components as we have moved to
DPDK v18.11.1 LTS.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This makes bitbake to pick up our layer-specific bb files as well
(as opposed to the previous setting of picking only bbappends) which
are only applied when that layer is included in our configuration.
This change is required for common/dpdk/recipes-entended/dpdk recipe.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds the latest stable release v18.11.1 LTS recipe of DPDK
which is based on meta-dpdk (thud) -> recipes-extended/dpdk/dpdk.inc
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This fixes the QA warnings regarding checksum mismatches
WARNING: mpv-0.28.2-r0 do_fetch: Checksum mismatch for local file /data/awais/mel/elm/downloads/waf
Cleaning and trying again.
WARNING: mpv-0.28.2-r0 do_fetch: Renaming /data/awais/mel/elm/downloads/waf to /data/awais/mel/elm/downloads/waf_bad-checksum_fbb646eafa430f959743010c85e269be
WARNING: mpv-0.28.2-r0 do_fetch: Checksum failure encountered with download of http://www.freehackers.org/~tnagy/release/waf-1.9.8;name=waf;downloadfilename=waf;subdir=mpv-0.28.2 - will attempt other sources if available
The download source was updated in the last upgrade but
we missed updating the checksums.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Package post-install intercept hooks that fail while do_rootfs and
generate a warning similar to this:
WARNING: development-image-1.0-r0 do_rootfs: The postinstall intercept
hook 'update_gio_module_cache' failed ...
are deferred for execution on first boot by marking the package as
"unpacked" instead of "installed" in:
oe-core/meta/lib/oe/package_manager.py
|-> run_intercepts()
|-> _postpone_to_first_boot()
|-> _handle_intercept_failure()
|-> .mark_packages("unpacked", registered_pkgs.split())
and the oe-core/meta/lib/oe/rootfs.py later on generates an ERROR as:
ERROR: development-image-1.0-r0 do_rootfs: The following packages
could not be configured offline and rootfs is read-only: ['gconf']
SWUpdate adds "read-only-rootfs" to the IMAGE_FEATURES, hence the
delayed pkg_postinst_* routines cannot be executed on the first boot
to configure the packages.
In case of gconf which is a dependency for Qt5, we remove
GIO_MODULE_PACKAGES so that update_gio_module_cache postinst-intercept
never applies to this package.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The security utils component clamav requires LLVM in a
similar manner like mesa so set the version that is in
use through our layer.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We know that multiple components depend on LLVM in a
way where they specify specific LLVM versions. We should
list all such through the conf fragment so they are
consolidated in a single place and we can identify
what needs to be changed/validated as LLVM's version
moves.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This works around a MEL bug and should be reverted
once the proper fix is in.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This sets the SWUpdate's CONFIG_GRUBENV_PATH so that when an update
is performed via HawkBit Server, it looks for the right grubenv file
to save_state into rather than going for the GRUBENV_PATH_DEFAULT
which does not exist in our case. Otherwise, update fails saying:
ERROR: Failed to open grubenv file: /boot/efi/EFI/BOOT/grub/grubenv
ERROR: Cannot persistently store update state.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
swupdate cleanup/fixes
|
|
Package post-install scripts that are explicitly set to be executed
ontarget and need to create/modify a file to configure the package
cannot execute on a read-only rootfs.
The oe-core/meta/lib/oe/rootfs.py generates an ERROR while do_rootfs:
ERROR: development-image-1.0-r0 do_rootfs: The following packages
could not be configured offline and rootfs is read-only: ['libomxil']
SWUpdate adds "read-only-rootfs" to the IMAGE_FEATURES, hence the
delayed pkg_postinst_ontarget_* routines cannot be executed on the
first boot to configure the packages.
Therefore as a work-around, in case of libomxil, we remove the
pkg_postinst_ontarget_* added in common/recipes-multimedia/libomxil.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
We explicitly disabled an swupdate specific post process command
on the initramfs image as it wasn't needed and didn't work well
for the image type. Since the rework of swupdate support this
post process command no longer exists so drop the unnecessary
fragment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The update image generation mechanism in swupdate configuration
has changed and we no longer support swupdate specific
IMAGE_FSTYPES so drop these otherwise we'll get a build time
error.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Package post-install intercept hooks that fail while do_rootfs and
generate a warning similar to this:
WARNING: development-image-1.0-r0 do_rootfs: The postinstall intercept
hook 'update_font_cache' failed ...
are deferred for execution on first boot by marking the package as
"unpacked" instead of "installed" in:
oe-core/meta/lib/oe/package_manager.py
|-> run_intercepts()
|-> _postpone_to_first_boot()
|-> _handle_intercept_failure()
|-> .mark_packages("unpacked", registered_pkgs.split())
and the oe-core/meta/lib/oe/rootfs.py later on generates an ERROR as:
ERROR: development-image-1.0-r0 do_rootfs: The following packages
could not be configured offline and rootfs is read-only:
['liberation-fonts']
SWUpdate adds "read-only-rootfs" to the IMAGE_FEATURES, hence the
delayed pkg_postinst_* routines cannot be executed on the first boot
to configure the packages.
Therefore as a work-around, in case of liberation-fonts, we remove the
pkg_postinst_<font-pkg> from all the FONT_PACKAGES added in
oe-core/meta/classes/fontcache.bbclass so that update_font_cache
postinst-intercept never applies to these packages.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Package post-install intercept hooks that fail while do_rootfs and
generate a warning similar to this:
WARNING: development-image-1.0-r0 do_rootfs: The postinstall intercept
hook 'update_pixbuf_cache' failed ...
are deferred for execution on first boot by marking the package as
"unpacked" instead of "installed" in:
oe-core/meta/lib/oe/package_manager.py
|-> run_intercepts()
|-> _postpone_to_first_boot()
|-> _handle_intercept_failure()
|-> .mark_packages("unpacked", registered_pkgs.split())
and the oe-core/meta/lib/oe/rootfs.py later on generates an ERROR as:
ERROR: development-image-1.0-r0 do_rootfs: The following packages
could not be configured offline and rootfs is read-only: [gdk-pixbuf]
SWUpdate adds "read-only-rootfs" to the IMAGE_FEATURES, hence the
delayed pkg_postinst_* routines cannot be executed on the first boot
to configure the packages.
Therefore as a work-around, in case of gdk-pixbuf, we remove the
pkg_postinst_<pixbuf-pkg> from all the PIXBUF_PACKAGES added in
oe-core/meta/classes/pixbufcache.bbclass so that update_pixbuf_cache
postinst-intercept never applies to these packages.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Package post-install intercept hooks that fail while do_rootfs and
generate a warning similar to this:
WARNING: development-image-1.0-r0 do_rootfs: The postinstall intercept
hook 'update_gio_module_cache' failed ...
are deferred for execution on first boot by marking the package as
"unpacked" instead of "installed" in:
oe-core/meta/lib/oe/package_manager.py
|-> run_intercepts()
|-> _postpone_to_first_boot()
|-> _handle_intercept_failure()
|-> .mark_packages("unpacked", registered_pkgs.split())
and the oe-core/meta/lib/oe/rootfs.py later on generates an ERROR as:
ERROR: development-image-1.0-r0 do_rootfs: The following packages
could not be configured offline and rootfs is read-only: ['glib-...']
SWUpdate adds "read-only-rootfs" to the IMAGE_FEATURES, hence the
delayed pkg_postinst_* routines cannot be executed on the first boot
to configure the packages.
In case of glib-networking, we remove GIO_MODULE_PACKAGES so that
update_gio_module_cache postinst-intercept never applies to this
package.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Fix multimedia-only build when graphics are not enabled
|
|
mpv: fix QA warning
|
|
gstreamer1.0-vaapi: fix mesa driver whitelist
|
|
Additional V1000 userspace updates for RTQA1 2019
|
|
amdgpu/v1000: RTQA1 2019 updates
|
|
This fixes the build failure when multimedia feature is enabled and
graphics is not.
GStreamer needs graphics to display videos. PACKAGECONFIGs of
gstreamer1.0-plugins-bad such as gles2, egl & vulkan depend on libdrm
and eventually on x11 for graphics requirement. In MEL for AMD, x11 is
only enabled when graphics feature is enabled.
Therefore, we disable the gles2, egl & vulkan PACKAGECONFIGs when
graphics are not available.
INTAMDDET-2686
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
Arsalan H. Awan
Wade Farnsworth
Awais Belal