| Age | Commit message (Collapse) | Author |
|---|
|
This adds LAYERSERIES_COMPAT warrior to common and all BSP layers, i.e.
* common
* v1000
* r1000
* snowyowl
* amdfalconx86
* steppeeagle
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the BSP and PATCH versions for MEL releases as these are
not applicable anymore.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This fixes the driver to report link status correctly otherwise
we run into situations where misleading timeout errors are
generated.
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Sumo
|
|
When spirom-test app is used to flash the BIOS to a version other
than the one that is already flashed on the board, the output says
that it all went successfully, but the BIOS/system doesn't boot up
after that at all.
The problem is with the chiperase function as it usually takes
time on other machines, but on snowyowl, it finishes the execution
instantly.
This fixes the issue allowing us to flash the BIOS on snowyowl
using the spirom-test app.
AMDDET-502
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Cleanup snowyowl
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes recipes-graphics from meta-snowyowl as they do not get
picked up because snowyowl does not have display interface support
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the leftovers from 08e1e59 in b7d8bab which are not
required anymore as it was fixed upstream -> oe-core -> 148fd7a
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The new release process and numbering requires these
versions being defined by each BSP.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Just like we've bisected for the XGBE fragment, this
now allows the eMMC patches to be overriden from other
BSPs which want to modify/drop the fragment.
We're dropping the fragment name from the snowyowl layer
SRC_URI because the common append now provides it already.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Separate out XGBE patches from the GPU patches fragment. We
apply this on all the BSPs and any BSP that wants to override
the fragment can simply provide the same named fragment from
its own layer.
We're dropping the fragment name from the snowyowl layer
SRC_URI because the common append now provides it already.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Just like the AMD XGBE patches we're now bisecting the
eMMC patches so different BSPs can provide a different
patchset while the most common piece will be kept in
the common layer.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We're trying to consolidate the common layer so it can be
used for multiple BSPs. This separates out the AMD XGBE
fragment so it can be overriden from elsewhere.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We're now supporting the 4.14 kernel.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
BBMASKs were setup for a few recipe appends from the common
layer so snowyowl builds could be performed cleanly. The
mask setup was inaccurate as it pertained to the development
build setup. This fixes that issue so the masks work more
generically in any environment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
These come in from meta-openembedded which is not a
dependecy for the snowyowl BSP at this time and hence
generate a build time error otherwise.
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>
|
|
|
|
This reverts commit 97734e5e31f0436ca1b966ef81f2a3813ef82190.
Network instabilities with 1 Gbps & 10 Gbps Copper SFPs were introduced
into amd-xgbe with this commit.
Fixes issue: AMDDET-503
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The upgraded version of lttng-modules from upstream
does not require the instrumentation backports so
drop them and update the version checking workaround
in order to fix the build.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The DPDK packages should only be tried when the dpdk
layer is in our configuration otherwise the packages
will not be found and a build error is seen.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
All the currently supported BSPs are 64bit so use the
appropriate m64 TUNE_FEATURE in order to get the build
environment evaluated properly. Otherwise the basic -m64
switch which is required for proper linker output
specification and other such things do not end up in
the correct form and the build fails in case a toolchain
that supports 32 and 64bit builds is used.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
Created IMAGE_FEATURES to be used by AMD BSPs removing all img.bbappends
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
defaults to no package included
snowyowl adds its own pkgs
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>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
|
|
The change being applied to the recipe is generic and
breaks whenever the recipe version is updated so use
a wildcard for versioning to keep it maintainable.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The backports for Spectre/Meltdown changes include things
that break the builds for lttng-modules otherwise these
changes. We get build failures such as
git/probes/../probes/lttng-tracepoint-event-impl.h:142:6: error: conflicting types for 'trace_kvm_mmio'
| void trace_##_name(_proto);
| ^
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
This moves the VIRTIO configs to the KVM configuration
fragment and enables CONFIG_VIRTIO_INPUT.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Use a light assignment (?=) so configurations can be
overridden from elsewhere.
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>
|
Arsalan H. Awan
Sudheesh Mavila
Wade Farnsworth
Awais Belal