Age | Commit message (Collapse) | Author |
|
amd-xgbe Sometimes driver report incorrect link status
|
|
This fixes the driver to report link status correctly otherwise
we run into situations where misleading timeout errors are
generated.
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Move changes from meta-r1000 to common
|
|
Upgrade DPDK to v18.11.1 LTS
|
|
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>
|
|
r1000 GA updates
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
mpv: update checksums for waf
|
|
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>
|
|
local.conf.append.v1000: whitelist x264 for commercial multimedia
|
|
The ffmpeg version in use for the v1000 depends on x264 so
we need to whitelist x264 in configurations where
INCLUDE_COMMERCIAL_MULTIMEDIA is enabled.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Fix SWUpdate enabled build with Qt5
|
|
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>
|
|
LLVM version setting for components
|
|
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>
|
|
amd-common-configurations: workaround a MEL bug
|
|
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>
|
|
SWUpdate: fix updates with HawkBit Server
|
|
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
|
|
Fix SWUpdate enabled build with Graphics and Multimedia
|
|
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>
|
|
v1000/rgp: upgrade to 1.3.1
|
|
Moving on to 1.3.1. The exact version is 1.3.1.71.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We will now be using the Host Security Tool for generating
update images and the templates will reside in the tool
itself.
Signed-off-by: Awais Belal <awais_belal@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>
|
|
v1000: upgrade vulkan components to 1.1.92
|
|
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>
|
|
This moves the vulkan bits for the v1000 platform to
1.1.92. The commit updates all the related components
in one go as the vulkan repositories have been reworked
to maintain things in a different way. This copes with all
the conflicts and dependencies.
The tools and headers components use patch version 0 whereas
the loader uses patch version 1 for a particular bug fix.
Signed-off-by: Awais Belal <awais_belal@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
|
|
Extra Packages Control using INCLUDE_<component>
|
|
amdgpu/v1000: RTQA1 2019 updates
|
|
V1000 OpenCV Integration
|
|
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>
|
|
This disables the wayland PACKAGECONFIG of gstreamer1.0-plugins-bad as
we do not support wayland.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Utilities such as the vainfo are provided through the libva-utils
package.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The fragment does not have any patch files left so drop
it as it is not a generic fragment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|