Age | Commit message (Collapse) | Author |
|
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>
|
|
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>
|
|
With recipe specific sysroots coming in to play each
package needs to handle its build dependencies more
strictly. This fixes such issues with vulkan-samples.
Signed-off-by: Awais Belal <awais_belal@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>
|
|
ffmpeg version upstream has moved on to 3.4.2 which
is better than what we have at the moment so simply
switch.
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>
|
|
Mesa v17.3.7 requires libdrm >= v2.4.89. Newer version is available at
poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb
The patches for libdrm were not applicable to the newer version. This
commit switches to the newer version and forward-ports the patches while
taking care of the changes introduced from libdrm v2.4.82 upto v2.4.91.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Switched from master branch to release_60 branch to get the actual
LLVM v6 which includes changes that are required by mesa v17.3.7
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This moves further common settings from the BSP
specific appends to the common fragment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This moves the upstream backports to the common layer
and uses an append to apply these so the same could
be used for other common changes.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The kernel 4.9 recipe is being used for v1000 as well
as snowyowl. Move the base recipe to common and then
use appends for BSP overrides.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports the speculation related patches up till
the 4.9.88 version from the linux-stable tree.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This backports the patches for Spectre/Meltdown from the stable-4.9
tree that are found between 4.9.81 and 4.9.85.
Additionally for now we've removed the disablement of IBPB as
that would likely be the last patch going in from our side otherwise
it will simply create conflicts while cherry-picking.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|