Age | Commit message (Collapse) | Author |
|
This renames common layers to meta-amd-bsp as it is going to hold all
the bsps in it in the following commits.
This also changes the layer title in layer.conf from "amd" to "amd-bsp"
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes mentor mel distro specific sato GUI config bits in
preparation for yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Created IMAGE_FEATURES to be used by AMD BSPs removing all img.bbappends
|
|
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>
|
|
The GTK module scriptlet fails to run as it utilizes qemu
which is currently not working for our BSPs due to lack of
a few instructions emulation on the qemu platform and warnings
are generated although the scriptlet is deffered till first
boot. The following warning is seen:
WARNING: Intentionally failing postinstall scriptlets of ['matchbox-keyboard-im', 'eudev-hwdb'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} ().
We now defer the scriptlet forcefully till the first boot to
cover up for the warning.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The AMD Vulkan ICD for v1000 is now integrated in the
layer so deploy it whenever INCLUDE_VULKAN is set.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This allows the user to leverage the INCLUDE_VULKAN
variable from local.conf and tell the build system
to deploy the required Vulkan bits on the target.
Enables support for v1000 machine.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
VULKAN_COMPONENTS, CODEXL_COMPONENTS needs to be assign
the default values for the machine other than amdfalconx86,
otherwise it generates a parsing error.
Also only populate CODEXL_COMPONENTS for amdfalconx86 machine,
as we do not support it for other machines.
Signed-off-by: Adeel Arshad <adeel_arshad@mentor.com>
|
|
bb.utils.to_boolean generates the parsing error when the
variable it is evaluating is not defined, so replace it with
bb.utils.contains which handles this case correctly.
Signed-off-by: Adeel Arshad <adeel_arshad@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>
|
|
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
We were installing mesa-demos by making it a runtime
recommendation for libgl-mesa. With the latest changes
on mesa package this scheme is no longer workable because
the recommendations for -mesa packages are handled differently.
We now install mesa-demos through core-image-sato and
core-image-base dependencies by making it a part of
IMAGE_INSTALL.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Conflicts:
common/recipes-benchmark/iperf/iperf_2.0.5.bbappend
common/recipes-core/initrdscripts/initramfs-live-install-efi_1.0.bbappend
common/recipes-core/initrdscripts/initramfs-live-install_1.0.bbappend
common/recipes-multimedia/gstreamer/gstreamer1.0-libav_%.bbappend
common/recipes-multimedia/mplayer/mplayer2_git.bbappend
meta-baldeagle/conf/machine/baldeagle.conf
meta-steppeeagle/conf/machine/steppeeagle.conf
|
|
The yocto standards specify that no layer should affect other
layers when it is not intended to be built. So machine, distro
or layer overrides should be used where ever possible to minimize
the impact of any such anomaly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
OE-Core has obsoleted the usage of base_contains function in favor
of the bb.utils.contains functions. The earlier one will be dropped
in coming releases of OE-Core.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Additional tools are only available when distro is set to mel.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Upgarde the owl-video app to support gstreamer 1.0.
This requires code changes to correspond to API changes
as well as configuration changes.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Change the dependent version of gstreamer for gaku to 1.0.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Use a simpler conditional setting to remove gaku in mel-lite builds.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Remove the gaku app when DISTRO=mel-lite to avoid the
gstreamer dependency since gstreamer is unsupported
in MEL Lite.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Since gstreamer is currently unsupported remove the one app
which depends on it.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|