Age | Commit message (Collapse) | Author |
|
This upgrades the amdgpu component of the xf86-video-amd
to 18.0.1.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We're now deprecating the LunarG SDK support but we'll still
keep basic Vulkan support in. The directory structure has
also been changed just to make it clear.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.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>
|
|
layer.conf/README.md: add meta-python as a dependency
|
|
All the GPU based BSPs use mesa as their GL. The newer
versions of mesa require python-mako on host (native) to
generate some build files and python-mako-native is only
available through meta-python at this time. The core
layer only provides python3-mako-native which is not
usable here.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This fixes vulkan-tools build (on sumo) by adding the missing
cxx flags in CMakeLists required for cross compilation
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds the build dependency for vulkan-samples on
glslang-native which is needed in sumo for this package due to
recipe specific sysroot requirement.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
LunarG SDK components upgraded to v1.1.70
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This updates the Vulkan Samples repository support
to the SDK version 1.1.70.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This updates the Vulkan Tools repository support
to the SDK version 1.1.70.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This updates the Vulkan loader and basic layers
support to the SDK version 1.1.70.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
As part of LunarG SDK upgrade to 1.1.70 spirv needs
to be updated.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
As part of LunarG SDK upgrade to 1.1.70 glslang needs
to be updated.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
MEL provides an additional graphics feature which is
required in order to support different types of images
under MEL.
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>
|
|
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>
|
|
This fixes
ERROR: opencl-1.0-r0 do_package_qa: QA Issue: /usr/lib64/libamdocl64.so contained in package opencl-amd-drivers requires libhsa-runtime64.so.1()(64bit), but no providers found in RDEPENDS_opencl-amd-drivers? [file-rdeps]
ERROR: opencl-1.0-r0 do_package_qa: QA Issue: /usr/lib64/libamdocl64.so contained in package opencl-amd-drivers requires libhsa-runtime64.so.1(ROCR_1)(64bit), but no providers found in RDEPENDS_opencl-amd-drivers? [file-rdeps]
The RDEPENDS are handled through the main package's dependencies.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
These changes were backported from OE-Core in the past
and are now present upstream for the current release.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
xserver-nodm-init_2.0 was upgraded to v3.0 in sumo. Therefore renaming
the bbappend from _2.0.bbappned to _%.bbappend
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
removing this line because it overrides PACKAGECONFIG[egl] which is
already set in mesa.inc. Also, no need to set --with-platforms here
because is is already being set in mesa.inc
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
When X server is launched it queries the kernel VT driver
for next free VT and as that particular kernel API is not
locked a race is sometimes seen between X server and
systemd's securetty and both try to acquire the same tty
that is tty1 an depending on what runs first either one of
these services, X server / securetty, fails on boot.
It has now become a tradition for many of the distros to
run X on vt7 and use VTs from 1-6 i.e. tty[1-6] for text
consoles so we'll just follow suite.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This force amdgpu to be loaded at boot time to avoid
xserver failures in various situations.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
OpenCL binary integration
|
|
This integrates various OpenCL components in the binary
form which can be utilized for runtime/development purposes.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This integrates the binary components of the Heterogeneous
System Architecture (HSA) which is required for the upcoming
OpenCL support.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This integrates the binary components of libhsakmt which
is required for the upcoming OpenCL support.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
Signed-off-by: Chaudhary Amit Kumar <chaudharyamit.kumar@amd.com>
|
|
There's no point in using the ttyUSB0 now as the
actual serial ports on the target are funtioning
as expected and this causes boot delays.
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>
|
|
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>
|
|
|
|
These configuration fragments are not required for the
v1000 builds and generate kernel configuration warnings
if included so drop them.
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>
|
|
Add amdvlk for v1000
|
|
|
|
This integrates the closed source AMD Vulkan ICD
library.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|