| Age | Commit message (Collapse) | Author |
|---|
|
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 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 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 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>
|
|
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>
|
|
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>
|
|
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>
|
Arsalan H. Awan
Awais Belal