Age | Commit message (Collapse) | Author |
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
We now default to the upstream version of libdrm which
is 2.4.81 and hence is much stable than the one we
were using earlier for AMD BSPs.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is a workaround for hang issues with compute shaders.
Signed-off-by: Ahsan Hussain <ahsan_hussain@mentor.com>
|
|
OGL 4.3 and kernel bug fixes
|
|
|
|
Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
|
|
The Vulkan integration mainly targets the MEL Commercial
configurations so the required tools should only be
populated in that particular case.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We have analyzed that the configuration variable INCLUDE_GAMING_COMPONENTS,
is no longer valid as the components it include are not particularly
specific to gaming. So we have splitted it into two configuration variables
INCLUDE_VULKAN and INCLUDE_CODEXL.
Signed-off-by: Adeel Arshad <adeel_arshad@mentor.com>
|
|
The machine configuration now includes a config fragment
that can be provided through customer layers. This will
help in situations where a variable can only be touched
through conf files rather than recipes one such example is
the SERIAL_CONSOLES variable.
Also pick up APPEND_ADDITIONAL which can be passed through
the same customer layer for flexibility.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The AMD_GNB_BUS was available under kernel 4.1 which
has been dropped during the upgrade to 4.4 so the
auto loading mechnism is not required anymore.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The glslangValidator is required for application
development on the host through CodeBench.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
As a best practise the serial consoles should be
provided earlier on the kernel command line than
the vga consoles because the last console is used
for taking user input and is mapped to /dev/console.
Using it differently can break things at places
where conflicting/incorrect serial drivers can
generate a kernel panic in such a scenario.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This commit does a few things which cannot be separated easily
so it cannot be split in to separate commits.
* Drops all 4.1 kernel bits.
* Moves all common patches from meta-amdfalconx86 to common.
* Moves SE/BE builds to 4.4 kernel.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
|
|
amdfalconx86: provide mechanism for enabling gaming components
|
|
multimedia: Add more license files for commercial multimedia
|
|
The newly added LunarG SDK components require a mechanism
to be pushed to target RootFS as well as to the ADE that
is being generated. The same inclusion handling should be
made available for any other gaming components such as
CodeXL that are integrated.
We now define a packagegroup (packagegroup-gaming) to
implement this mechanism and provide a variable in local.conf
for amdfalconx86 to enable these components.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Some components that are required for the I2S audio
to work correctly are part of the AMDGPU driver like
the amd_gnb_bus. The AMDGPU driver is not RT safe yet
so it is disabled which makes the RT builds fail.
We now disable these failing components on the RT
kernel builds to cover up the issue.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This allows for later overriding by other local.conf.append files
using ??= while still allowing a local user to override them all
by using =.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This has been removed from poky so we no longer reference it.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This consolidates the common configurations between the
different machines and move them to common from where
these are used through an include to make things more
maintainable.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
Powerplay is by default disabled for CZ and clones.
So we need to explicitly enable using amdgpu.powerplay=1
in the machine configuration file.
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
DAL is enabled by default and should be functioning
correctly. So removed amdgpu.dal=0 from machine
configuration file.
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
install AMD ASoC ACP-12S driver only on non-embedded hardware by
checking 6th bith of iGPU rev ID.
|
|
meta-amd: add code to support falcon family
|
|
Powerplay is by default disabled for CZ and clones.
So we need to explicitly enable using amdgpu.powerplay=1
in the machine configuration file.
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
DAL is enabled by default and should be functioning
correctly. So removed amdgpu.dal=0 from machine
configuration file.
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
|
|
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
The disclaimer text for license-restricted packages is updated
to align with the other standard MEL BSPs. Additionally some
minor refactoring is done for the same alignment needs.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Sanjay Mehta <sanju.mehta@amd.com>
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
(cherry picked from commit 6e1085aa42c9a071e028f4d3d69d70478509b78d)
|
|
QEMU does not currently support the enhanced instructions available
on the AMD chips. Some builds with external toolchains will fail
if these instructions are enabled by default.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
|
|
Imc support
|
|
It is seen that when a boolean variable isn't enabled,
there's no change to the value at all, not even a space
if += is used.
So in order to cope with the value exactly and to avoid
un-intended results we use .= to strengthen the logic.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
- amdfalconx86 / SteppeEagle: IMC and AMD SPI SDK
- BaldEagle: Enable IMC
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
Signed-off-by: Michael Powell <michael_powell@mentor.com>
|