Age | Commit message (Collapse) | Author |
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
MEL Lite: glibc updates for various packages
|
|
This drops the do_compile override which was done to support build
with external & multilib toolchains as it is merged upstream now.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The -march flag used in compilation of DPDK defaults to an
Intel specific machine i.e. "corei7", whereas snowyowl's arch is
different.
It is required by DPDK to set the var DPDK_TARGET_MACHINE accordingly.
This sets the DPDK_TARGET_MACHINE (effectively fixes -march flag)
according to target's ARCH i.e. znver1, which is one of the supported
architectures in DPDK.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This is an upstream backport required for MEL Lite which
is based on glibc 2.28.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
amd-features/common-configs: consolidate further
|
|
Fixes build with glibc 2.28+ with a backport from
oe-core master. MEL lite is based on gcc8.2 which
in turn requires glibc 2.28 hence the fix is needed
here conditionally.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports a fix from oe-core master in order
to fix the build for mel lite which is based on the
glibc 2.28.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports fixes from mainline hdparm in order
fix build with glibc 2.28+, needed for mel lite.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is essentially a backport from oe-core master
and required for mel-lite as it uses gcc8.2 based on
glibc 2.28
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This modifies ppp to use openssl for crypt in
order to fix build with glibc 2.28+ otherwise
many different failures are seen.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports a patch from coreutils 8.30 which
fixes the build with glibc 2.28+ tools. Needed for
mel lite.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is actually a backport from upstream oe-core
as the mentioned fix is not available for sumo and
mel lite will be using gcc8.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The x11 machine feature is now only broadcasted when
user is looking for graphics through EXTRA_IMAGE_FEATURES.
Additionally refine the feature packages in a way such that
a subset of multimedia can be used even when graphics is not
included as a feature.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This upgrades DPDK to the latest stable release v18.02.2
according to upstream meta-dpdk -> sumo
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
MEL is now basing its features in a way that disregard
which _particular image_ is being built and gives this
flexibility to user where they can decide which extra
features should be populated. This is manipulated in the
local.conf using EXTRA_IMAGE_FEATURES.
This aligns the AMD features accordingly and basis all
functionality on EXTRA_IMAGE_FEATURES. This would help
minimize the risk of going off track with feature manipulation
while doing open as well as MEL based builds.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This fixes dpdk compilation by overriding the meta-dpdk's
do_compile function. dpdk's GNUmakefiles do a lot of
manipulation to the Compiler and Linker flags and therefore
cross compilation breaks with a multilib toolchain.
This commit adds the missing LDEMULATION flags (via TUNE_LDARGS)
required by linker, and also adds --no-sysroot-suffix to the CFLAGS
which also does not get to the compiler for the way makefiles
manipulate the flags, hence linking breaks.
The reason we are still keeping the unset LDFLAGS etc is again
the way makefiles manipulate the linker flags. They prefix "-Wl,"
to all the linker flags that come via LDFLAGS, TARGET_LDFLAGS &
BUILD_LDFLAGS even if there is already "-Wl," prefixed.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds the dpdk's build dependency on "openssl" as dpdk
ccp crypto driver requires openssl headers in the sysroot.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The new bitbake scheme does not allow fuzzes in the
patches and throws a warning if one is seen. This fixes
WARNING: boost-1.59.0-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
...
Applying patch boost-math-disable-pch-for-gcc.patch
patching file libs/math/build/Jamfile.v2
Hunk #1 succeeded at 13 with fuzz 1.
...
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is now being handled through MEL's config and package
handling is done through features so there's no need of the
setting anymore.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
MEL specifically provides additional components under the
multimedia feature which we need to support here.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This moves the libdrm updates from the v1000 layer to
common so all BSPs can leverage the support and the
maintenance burden is minimized.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The patch file is not being used and is probably a
leftover from an older cleanup.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This moves all the basic changes from meta-v1000,
which has the latest mesa version, to the common layer
so that all BSPs can leverage the latest support.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
amd-misc-pkgs (previously named as amd-common-pkgs) is intended for:
* Platform Specific Packages
* Common Packages to be added to all machines
* ...and others that may not fall into any feature category, etc.
Also added var AMD_PLATFORM_SPECIFIC_PKGS for any platform specific
misc pkgs etc.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The multimedia feature is not a common feature and should
only be deployed on supporting platforms. For now, we'll
install these for GPU enabled targets.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
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
|