Age | Commit message (Collapse) | Author |
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
SWUpdate Failsafe Implementation
|
|
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>
|
|
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>
|
|
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <Chaudharyamit.Kumar@amd.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
m4: drop patches already incorporated upstream
|
|
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>
|
|
This was done in 165f830fda9fbde5feef4c336ceb7c95532a635d but
used a different override than what was required.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|