aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2019-06-19Merge pull request #638 from smavila/sumosumoWade Farnsworth
amd-xgbe Sometimes driver report incorrect link status
2019-06-19amd-xgbe Sometimes driver report incorrect link statusSudheesh Mavila
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>
2019-06-17Merge pull request #637 from abelal/r1k-commonWade Farnsworth
Move changes from meta-r1000 to common
2019-06-17Merge pull request #634 from ArsalanHAwan/upgrade-dpdkWade Farnsworth
Upgrade DPDK to v18.11.1 LTS
2019-06-12mesa: move updates from meta-r1000 to commonAwais Belal
This allows usage of the mesa upgrade on BSPs other than the r1000 as well. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-06-12linux-yocto: move updates from meta-r1000 to commonAwais Belal
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>
2019-05-22common/dpdk: remove the older DPDK v18.02.2 componentsArsalan H. Awan
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>
2019-05-22common/layer.conf: include bb files too from layer specific dirsArsalan H. Awan
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>
2019-05-22common/dpdk: add DPDK v18.11.1 LTS recipeArsalan H. Awan
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>
2019-04-30Merge pull request #633 from abelal/rework_r1k_632Wade Farnsworth
r1000 GA updates
2019-05-01r1000/mesa: fix QA patch warningsAwais Belal
Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-05-01r1000/mesa: update for GA releaseAwais Belal
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com> Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-05-01r1000: amdgpu xgbe mmc update for GAAwais Belal
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com> Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-04-23Merge pull request #631 from abelal/sumoWade Farnsworth
mpv: update checksums for waf
2019-04-23mpv: update checksums for wafAwais Belal
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>
2019-04-18Merge pull request #630 from abelal/sumoWade Farnsworth
local.conf.append.v1000: whitelist x264 for commercial multimedia
2019-04-17local.conf.append.v1000: whitelist x264 for commercial multimediaAwais Belal
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>
2019-04-10Merge pull request #628 from ArsalanHAwan/swu-qt5Awais Belal
Fix SWUpdate enabled build with Qt5
2019-04-10common/swu/gconf: rm failing postinsts delayed till first bootArsalan H. Awan
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>
2019-04-05Merge pull request #627 from abelal/clamavAwais Belal
LLVM version setting for components
2019-04-05amd-common-configurations: set CLAMAV_LLVM_RELEASEAwais Belal
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>
2019-04-05common/mesa: move LLVM version binding to confAwais Belal
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>
2019-04-04Merge pull request #626 from abelal/wa_dmAwais Belal
amd-common-configurations: workaround a MEL bug
2019-04-04amd-common-configurations: workaround a MEL bugAwais Belal
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>
2019-03-29Merge pull request #625 from ArsalanHAwan/swu-with-hawkbitWade Farnsworth
SWUpdate: fix updates with HawkBit Server
2019-03-29common/swupdate: set GRUBENV_PATH to fix updates with hawkbit serverArsalan H. Awan
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>
2019-03-21Merge pull request #623 from abelal/swupdate_v1kAwais Belal
swupdate cleanup/fixes
2019-03-21Merge pull request #622 from ArsalanHAwan/swu-graphics-multimediaAwais Belal
Fix SWUpdate enabled build with Graphics and Multimedia
2019-03-21common/swu/libomxil: rm pkg_postinst_ontarget_* because of RO rootfsArsalan H. Awan
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>
2019-03-20Merge pull request #624 from abelal/v1k-userspaceWade Farnsworth
v1000/rgp: upgrade to 1.3.1
2019-03-20v1000/rgp: upgrade to 1.3.1Awais Belal
Moving on to 1.3.1. The exact version is 1.3.1.71. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-20v1000: drop swupdate template filesAwais Belal
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>
2019-03-20core-image-minimal-install-initramfs: drop overrideAwais Belal
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>
2019-03-20amd-common-configurations: adjust IMAGE_FSTYPES for swupdateAwais Belal
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>
2019-03-20Merge pull request #621 from abelal/v1k-userspaceAwais Belal
v1000: upgrade vulkan components to 1.1.92
2019-03-20common/swu/liberation-fonts: rm failing postinst delayed til first bootArsalan H. Awan
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>
2019-03-20common/swu/gdk-pixbuf: rm failing postinsts delayed til first bootArsalan H. Awan
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>
2019-03-20common/swu/glib-networking: rm failing postinsts delayed til first bootArsalan H. Awan
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>
2019-03-19v1000: upgrade vulkan components to 1.1.92Awais Belal
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>
2019-03-18Merge pull request #620 from ArsalanHAwan/multimedia-wo-graphicsWade Farnsworth
Fix multimedia-only build when graphics are not enabled
2019-03-18Merge pull request #619 from abelal/mpvWade Farnsworth
mpv: fix QA warning
2019-03-18Merge pull request #618 from abelal/gst-vaapiWade Farnsworth
gstreamer1.0-vaapi: fix mesa driver whitelist
2019-03-18Merge pull request #617 from abelal/v1k-userspaceWade Farnsworth
Additional V1000 userspace updates for RTQA1 2019
2019-03-18Merge pull request #616 from ArsalanHAwan/extra-pkgs-controlWade Farnsworth
Extra Packages Control using INCLUDE_<component>
2019-03-18Merge pull request #615 from chaudharyak/sumoWade Farnsworth
amdgpu/v1000: RTQA1 2019 updates
2019-03-18Merge pull request #614 from ArsalanHAwan/v1k-integrate-opencvWade Farnsworth
V1000 OpenCV Integration
2019-03-18common/gstreamer: fix multimedia-only build when graphics arent enabledArsalan H. Awan
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>
2019-03-18common/gstreamer: wayland isnt supported so remove it from plugins-badArsalan H. Awan
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>
2019-03-18libva: deploy va utils when availableAwais Belal
Utilities such as the vainfo are provided through the libva-utils package. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-18r1000/linux-yocto: drop unnecessary patch fragmentAwais Belal
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>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-25 12:35:26 +0000