aboutsummaryrefslogtreecommitdiffstats
path: root/common
AgeCommit message (Collapse)Author
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-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-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-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-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-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-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-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 #615 from chaudharyak/sumoWade Farnsworth
amdgpu/v1000: RTQA1 2019 updates
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-18xserver-nodm-init: switch X to VT7 for all amdgpu platformsAwais Belal
Rather than applying the setting specifically to some BSPs we do this for all the amdgpu enabled targets. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-18ffmpeg: enable vaapi for amdgpu targetsAwais Belal
This simply enables the vaapi config of ffmpeg through the common layer depending conditionally on the amdgpu override so we don't have to specify the setting for separate BSPs. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-18mesa/llvm: move to common layer from r1000Awais Belal
All targets are being aligned on the same mesa and llvm versions so move configurations to the common layer. This upgrades llvm to v7 and mesa to 19.0.0 for all platforms. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-18mpv: fix QA warningAwais Belal
This fixes WARNING: mpv-0.28.2-r0 do_populate_lic: Could not copy license file Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-15Merge pull request #604 from ArsalanHAwan/swu-failsafeAwais Belal
SWUpdate Failsafe Implementation
2019-03-15gstreamer1.0-vaapi: fix mesa driver whitelistAwais Belal
The gstreamer-vaapi plugins detect the driver by matching driver info with a whitelist. As Mesa updated its vaapi driver info the whitelist failed to work for the Mesa drivers. This fixes the whitelist by back porting an upstream patch. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-14libdrm: move from r1000 to common (v2.4.96)Awais Belal
All platforms are being aligned on the same version of libdrm so moving it to common makes sense. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-03-13libdrm : updated amdgpu ids fileChaudhary Amit Kumar
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
2019-03-13amdgpu : RTQA1 2019 kernel patch backportedChaudhary Amit Kumar
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
2019-03-08swupdate/amd-wdt: do not stop wdt as swupdate implementation needs itArsalan H. Awan
Mentor SWUpdate as a part of its Failsafe Update mechanism implementation requires the WDT to keep running. So lets not disable it. Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2019-03-08swupdate/initrdscripts: integrate amd-wdt in GRUB cfg for SWU failsafeArsalan H. Awan
This alters the init-install-efi.sh script by integrating the AMD-WDT in GRUB cfg of MEL installation to implement SWUpdate Failsafe Update mechanism. The AMD Watchdog is started as soon as a menuentry is selected by calling the setup_wdt function. It sets the WDT timeout of 60s by default which can be changed as needed. We also introduce a variable "mel_wdt" which allows user to disable the WDT in case the user is doing kernel debugging or so and wants the system to keep running. If WDT is detected to be fired & SWU was performed, then we fallback to last working state, else we do a normal boot. Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2019-03-06swupdate/grub: AMD Watchdog Driver & API support for GRUB cfg/consoleArsalan H. Awan
SWUpdate Failsafe Update mechanism requires watchdog timer support to detect a failed update, and to get the WDT triggered in case of a system hang for that matter. This adds AMD Watchdog Driver & Watchdog API support for GRUB allowing us to access and configure the WDT from GRUB configuration and console. Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2019-02-25systemd: fix mmc device dissectionAwais Belal
The systemd gpt autogenerator dissects each device for partition information. MMC devices having special partition layout containing fixed boot0/1 and rpmb partitions cause a failure during dissection and during boot we get: systemd-gpt-auto-generator[102]: Failed to dissect: Input/output error The fix is an upstream backport. https://github.com/endlessm/systemd/pull/81 Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-02-20amd-common-conf: specify MEL supported IoT packagegroupsArsalan H. Awan
This specifies the supported MEL IOT_PACKAGES for AMD BSPs as required by mel-iot layer. Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2019-02-15libdrm: use a more aligned value for PVAwais Belal
This is more of a good practise and lets the user know the exact version more easily rather than digging through the source. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-02-08Merge pull request #601 from abelal/update_manifestWade Farnsworth
m4: drop patches already incorporated upstream
2019-02-08m4: drop patches already incorporated upstreamAwais Belal
These patches are now present in oe-core so we do not need to keep a copy here. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-02-08systemd: fix udev-hwdb postinst disablementAwais Belal
This was done in 165f830fda9fbde5feef4c336ceb7c95532a635d but used a different override than what was required. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-29amd-common-configurations: disable SWDESC_INCLUDE_BOOT_FILESAwais Belal
While creating the .swu through MEL's swupdate classes the contents of IMAGE_BOOT_FILES are processed in order to collect all the artifacts. While our BSPs produce a live image containing the rootfs as a loop device in the boot partition. This creates a circular dependency where the do_image_ext4 starts depending on itself. Fix this by forcing swupdate classes to not include these boot files. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-29amd-common-configurations: provide swupdate supportAwais Belal
This enables swupdate support for the AMD platforms by providing swupdate as its machine features depending on the available layers. Also, fixes a few variables required by MEL's swupdate implementation. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-29initramfs-module-install-efi: manipulate the installer for SWUpdateAwais Belal
This fixes/modifies things as per the SWUpdate support being implemented for the MEL platforms. Covers the following 1. partitioning scheme as per dual-copy approach. 2. drop blacklist of the boot device in installed image required by swupdate. 3. deploy kernels and rootfs as <image>A to conform with dual copy approach. 4. implement grub.env approach to pick up kernel and rootfs from the environment to support fallback mechanism. 5. implement fallback mechanism. 6. do not set rootfs as rw, the MEL scheme is to use ro when supporting swupdate. 7. do not set a timeout for grub menu in installed image as this will simply delay boot. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-18swupdate: basic support for AMD platformsAwais Belal
This enables GRUB under SWUpdate which is the bootloader used by AMD platforms and deploys the bl-kernels files in accordance with the support being enabled for AMD platforms. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-18core-image-minimal-install-initramfs: drop illegal POST process cmdAwais Belal
The sw-description is not available for initramfs images so drop the post process commands as it fails otherwise. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-18glib-2.0, udev-hw_db: disable postinstall hooksAwais Belal
GIO modules and udev's hw_db requires postinstallation hooks which fail due to current tools not supporting qemu execution on AMD builds. So, such hooks are deferred to first-boot which in case of swupdate is not possible as the rootfs is read-only. Simply disable these postinstall hooks. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-17Merge pull request #596 from abelal/minor_fixesWade Farnsworth
Minor fixes
2019-01-17amd-common-configurations: fix MACHINE_FEATURES manipulationAwais Belal
Not using immediate expansion causes circular dependencies in some cases so avoid such issues while depending on EXTRA_IMAGE_FEATURES. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-17amd-common-configurations: drop syslinux supportAwais Belal
We do not support legacy boots so using syslinux does not make any sense at the moment and dropping such metadata would allow easier maintenance. Signed-off-by: Awais Belal <awais_belal@mentor.com>
2019-01-11Merge pull request #594 from abelal/dockerWade Farnsworth
linux-yocto_4.14: enable configurations to support docker
2019-01-10Revert "common/conf: remove vmlinux from KERNEL_IMAGETYPES..."Arsalan H. Awan
This reverts commit 570b7302369a337111cb247cebe19e0ec0e47ccb as it is fixed in meta-mentor->sumo: 922ef38be26e22b98a15388f66fa0d2770d50cc0 Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
2019-01-04linux-yocto_4.14: enable configurations to support dockerAwais Belal
This enables kernel configurations to be able to support the virtualization feature, the goal for now is to simply support docker not the whole virtualization layer. Signed-off-by: Awais Belal <awais_belal@mentor.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-26 15:15:28 +0000