Age | Commit message (Collapse) | Author |
|
The ffmpeg version in use for the v1000 depends on x264 so
we need to whitelist x264 in configurations where
INCLUDE_COMMERCIAL_MULTIMEDIA is enabled.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This moves the vulkan bits for the v1000 platform to
1.1.92. The commit updates all the related components
in one go as the vulkan repositories have been reworked
to maintain things in a different way. This copes with all
the conflicts and dependencies.
The tools and headers components use patch version 0 whereas
the loader uses patch version 1 for a particular bug fix.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Additional V1000 userspace updates for RTQA1 2019
|
|
All targets are being aligned on the same mesa and llvm
versions so move configurations to the common layer.
This upgrades llvm to v7 and mesa to 19.0.0 for all
platforms.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
To use a single description for all INCLUDE_<components> alongwith
the supported <component> summary in each BSP's local.conf.
This also helps to have a single place for all the configurable
<components> in the local.conf instead of having huge paragraph
for each <component> and having to scroll to find each <component>.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This introduces var INCLUDE_OPENCV into local.conf to control the
inclusion of OpenCV into the image. If user needs OpenCV, they can
add it by setting INCLUDE_OPENCV = "yes" in the local.conf.
This helps in keeping the image size smaller if user doesn't need it.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This introduces var INCLUDE_OPENCL into local.conf to control the
inclusion of OpenCL into the image. If user needs OpenCL, they can
add it by setting INCLUDE_OPENCL = "yes" in the local.conf.
This helps in keeping the image size smaller as OpenCL consumes a
lot of disk space.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This integrates the OpenCV library and samples based on C++
and Python APIs.
The integrated samples contain various apps for image and video
processing demonstration using OpenCV, including using image/video
files as well as camera as input. The demos work best with the
"graphics" and "multimedia" features enabled.
Also, this removes v4l bits from OpenCV as we do not
support Video4Linux.
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>
|
|
v1000/amdfalconx86: drop deprecated packages from installation
|
|
We deprecated the LunarG SDK in one of the previous updates
but missed one instance where these packages were being
explicitly installed on the target, this generates a build
time error. Fix this by dropping the deprecated packages from
the installation list.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.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>
|
|
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>
|
|
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>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@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>
|
|
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>
|
|
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>
|
|
|
|
This moves the mesa version for v1000 BSP to align with
meta-amd's common layer as well as upstream. This allows
for better and easier maintainability.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The v1000 platform does not support grub in legacy mode
with a dual boot setup which is required in case of the
MEL Lite release cycle. Drop grub and use grub-efi for
the BSP in order to cope up with the change.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Upstream has dropped the git based recipe for mesa
so we follow the same approach. This starts using
a versioned recipe with the main recipe file is
created under the same layer with the intention of
dropping once upstream moves to version 17.3.
Patches have been adjusted accordingly with configuration
requirements fulfilled as well.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
This is a requirement for some QA test cases where ffmpeg
is needed on target.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
V1000 patch release
|
|
The component will not be supported on the V1000
platform.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
v1000.conf: adjust CB understandable cpu for v1000 ADE support
|
|
Signed-off-by: Avinash M N <avimn@amd.com>
|
|
This enables getty on ttyS4/ttyS5 as well as
providing kernel console on the ttyS4 port.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
CodeBench defines its particular CPUs for ADE integration and
the cpu for v1000 is now adjusted accordingly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This is mainly targeted against master branch builds.
Doing it now has the advantage that the change makes
it in for any releases prior to moving to the master
branch.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The feature will not be available for the current
release so drop it altogether.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The current BSP isn't sufficient to make the
actual RS232 ports work so we'll use the USB
port as console for now.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
|