| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The new MEL structure requires x11 in machine configurations
for targets that require X11/GUI based images otherwise x11
is dropped from the distro.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Created IMAGE_FEATURES to be used by AMD BSPs removing all img.bbappends
|
|
This backports the speculation related patches up till
the 4.9.111 version from the linux-stable tree.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Graphics components to depend on "IMAGE_FEATURES" > "x11-base"
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
"gstreamer1.0-meta-x11-base" to depend on "IMAGE_FEATURES" > "x11-base"
"gstreamer1.0-meta-audio" to depend on "IMAGE_FEATURES" > "tools-audio"
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
defaults to no package included
snowyowl adds its own pkgs
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This makes configurable feature component variables to use a standardized
naming convention i.e. should end with _PKGS instead of _COMPONENTS or
_PACKAGES
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This defines AMD Features that can be added as EXTRA_IMAGE_FEATURES
to different machines based on what is supported on a machine. This adds
a broad flexibility and control over packages being installed on a
machine for any image without needing to create bbappends for all the
images that are to be supported.
> Each feature can contain packages and packagegroups as its components.
> Feature components can be dependent on DISTRO, IMAGE_FEATURE, or any
variable in general. e.g.: Components of "amd-feature-graphics" may be
dependent on "x11-base" as an IMAGE_FEATURE. Some packages may only be
included for a specific DISTRO. Some packages may only be installed if
user allows them in local.conf etc.
> Each machine must add the required features to EXTRA_IMAGE_FEATURES in
its own machine config file.
> All required features must be added to a machine regardless of the
image being built, but make sure that feature components are included
based on dependency conditions. e.g. say "amd-feature-graphics" was
added to a machine that supported graphics, but components of this
feature must not be installed on an image that is only console based
such as "core-image-base", therefore such components must depend on an
IMAGE_FEATURE that is based on graphics such as "x11-base".
> Each machine can also override feature components in its own machine
config when adding the feature to EXTRA_IMAGE_FEATURES. e.g.: a
feature may be added to a specific machine with minimal (or extended)
packages based on requirement.
Features are classified as:
* amd-common-pkgs : Common pkgs to be added to all machines
* amd-feature-multimedia : Multimedia packages (it does not depend
on graphics because a machine may not
have a GUI but could play videos and
sounds from console)
* amd-feature-graphics : Graphics packages
* amd-feature-networking : Networking packages
* amd-feature-debug-profile : Debugging and Profiling tools
* More features may be added later as needed
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The GTK module scriptlet fails to run as it utilizes qemu
which is currently not working for our BSPs due to lack of
a few instructions emulation on the qemu platform and warnings
are generated although the scriptlet is deffered till first
boot. The following warning is seen:
WARNING: Intentionally failing postinstall scriptlets of ['matchbox-keyboard-im', 'eudev-hwdb'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} ().
We now defer the scriptlet forcefully till the first boot to
cover up for the warning.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports the speculation related patches up till
the 4.9.107 version from the linux-stable tree which
includes mitigation for Spectre v4 as well.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The upcoming mitigations for Spectre/Meltdown are addressed in a way
that a patch contains fixes on a topic for both normal/KVM running
modes. If we do not backport the earlier KVM patches the conflicts
will be very hard to resolve.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
This includes spectre/meltdown backports for the
RT kernel as well by moving the patches fragment
to the common include.
A patch that conflicts with RT changes has been
taken out of the backport set and added separately
for both type of kernels after adjusting accordingly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This moves the parts that can be utilized through the
common layer for the RT kernel and generalizes the
support.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This will allow for an easier maintenance procedure such that
the common fragments can be handled more seamlessly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
A commit was missed during backports which generates failure
during build. This now picks that commit up as well and updates
the series appropriately.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Add amdvlk for v1000
|
|
|
|
AMD Spectre/Meltdown Upstream backports
|
|
The AMD Vulkan ICD for v1000 is now integrated in the
layer so deploy it whenever INCLUDE_VULKAN is set.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The correct way of using a license is through the common_licenses
from the meta layer so use that appropriately. This also silents
the warning
WARNING: packagegroup-multimedia-risky-1.0-r0 do_populate_lic: ${COREBASE}/LICENSE is not a valid license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM. This will become an error in the future
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Drop layer specific recipe and leverage the upstream
one which is more recent. This would also make the
maintenance feasible.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The intention with this post-installation script is to
run it on the target at first boot so handle it
accordingly otherwise it will only generate warnings
on build time.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The intention with this post-installation script is to
run it on the target at first boot so handle it
accordingly otherwise it will only generate warnings
on build time.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
gstreamer1.0-vaapi is now provided through oe-core so
we do not have to maintain an outdated version ourselves.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Between all the merges and reverts we mixed up a
few things and ended up with a wrong configuration
for MEL builds. This drops the unneccesary bits to
fix such things.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
oe_filter_out has been deprecated.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is now an upstream requirement for compliance
and throws warnings on the console if not handled
appropriately.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The udev rule for hotplug was getting triggered multiple times
at system boot-up even when there was no occurance of a hotplug event.
This generates a huge stream of DRM events at startup, observable in
kernel logs, resulting in system boot-up delays.
This commit fixes the udev rule by making use of the HOTPLUG uevent
environment variable that is set by the uevent drm_sysfs_hotplug_event
generated by DRM sysfs class at the time of a hotplug:
kernel_source/drivers/gpu/drm/drm_sysfs.c
That way, the udev hotplug rule is only triggered at the time of a
DRM hotplug, as it should.
Fixes issue: INTAMDDET-2306
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
DPDK + Strongswan for Snowy Owl
|
|
This moves the upstream backports to the common layer
and uses an append to apply these so the same could
be used for other common changes.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The kernel 4.9 recipe is being used for v1000 as well
as snowyowl. Move the base recipe to common and then
use appends for BSP overrides.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This reverts commit e49d7b4d2e58ec381f059ca87539857abf16d389.
|
|
This drops some packages which were merged unintentionally
under
https://github.com/MentorEmbedded/meta-amd/commit/2b7369b74af7b8c533fb061a5856ddb029ec0ff8
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This reverts commit 2b7369b74af7b8c533fb061a5856ddb029ec0ff8.
|
|
This reverts commit 653568002d28efdc388d7ccc09b7c82310b7b3f2.
|
|
|
|
Install the strongswan package conditionally for
the snowyowl BSP only.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This installs various dpdk components on the target
RFS conditionally for snowyowl BSP only at the
moment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This forces the build system to deploy build artifacts
such as examples and tests under /usr/share/dpdk/.
Earlier the output would populate directly under
/usr/share which is not very convenient for identifying
what the package actually provides.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This fixes shared library builds for CCP and
AXGBE drivers and provides a way of selecting
the sort of build user requires however there
are some caveats of using a shared mode build
and this has been documented with the change.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This enables support for the AXGBE driver found on the
snowyowl BSP. The patches have been backported from the
upstream dpdk project.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This enables the dpdk framework for the snowyowl
BSP and backports the patches for the crypto hardware
CCP from the main dpdk project.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This enables dri3 under Mesa for v1000.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This updates a few internal patches that we have for
initramfs installation scripts to align with the
upstream updates. Otherwise the do_patch phase for
the intended packages fails to go through cleanly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Cleaned up indentation issues as the file was pretty
messed up. The OE guidelines suggest using 4 spaces
and no tabs.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This enables the Xorg TearFree option for the
AMDGPU to cope with various tearing issues.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
Awais Belal
Wade Farnsworth
Arsalan H. Awan