| 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 the linux-yocto_4.4 & linux-yocto-rt_4.4 kernel recipes
as we don't need them anymore.
This also sets the PREFERRED_VERSION_linux-yocto ?= "4.14%" as default
kernel for all bsps. We still have snowyowl and v1000 using the 4.14
kernel. r1000 has moved to 4.19 kernel.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the gst-examples from GSTEXAMPLES variable from
packagegroup-core-x11-sato.bb in case INCLUDE_COMMERCIAL_MULTIMEDIA is
not set to "yes".
This is required to be done to fix the following dependency on faad2
which has commercial LICENSE_FLAGS:
Missing or unbuildable dependency chain was: ['core-image-sato',
'packagegroup-core-x11-sato', 'gst-examples',
'gstreamer1.0-plugins-bad', 'faad2']
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes gstreamer1.0-vaapi from GSTREAMER_PKGS (amd-features.inc)
in case INCLUDE_COMMERCIAL_MULTIMEDIA is not set to "yes".
This is required to be done to fix the following dependency on faad2
which has commercial LICENSE_FLAGS:
Missing or unbuildable dependency chain was: ['core-image-sato',
'gstreamer1.0-vaapi', 'gstreamer1.0-plugins-bad', 'faad2']
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds a new file amd-multimedia.inc and sets it to be required in
amd-common-configurations.inc.
The purpose of this file is to control the multimedia packages and mpv
which have LICENSE_FLAGS = "commercial".
We do this using INCLUDE_COMMERCIAL_MULTIMEDIA and INCLUDE_MPV flags
which control these packages from being included into the builds unless
user explicitly sets these variables to "yes" in the local.conf.
This also adds a disclaimer that we don't include these by default and
we don't distribute these as binaries.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This also sets the *_LLVM_RELEASE vars in amd-common-configurations.inc
accordingly.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds wic.bmap to IMAGE_FSTYPE so that whenever a wic image is
generated, its wic.bmap file is also created. This bmap file can be
fed to bmaptool to make the image write process faster as bmaptool
would only try to write storage space that is mapped to actual data
rather than also writing the free space part to the disk and waisting
time there. This data mapping comes from this bmap file.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds LAYERSERIES_COMPAT warrior to common and all BSP layers, i.e.
* common
* v1000
* r1000
* snowyowl
* amdfalconx86
* steppeeagle
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This upgrades llvm from v7 to v8.0.0 according to yocto warrior
branch recipes.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes inclusion of firmware-wireless pkg which is required in
mentor's mel/mel-lite distros.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes a workaround for a mentor's mel related issue that is no longer
applicable.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor iot packagegroups setting as required by the
mel-iot layer that is no longer supported for AMD BSPs.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the condition that multimedia & networking pkgs should
only be included when mentor distro mel is being built.
This is being done in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Mentor's mel/mel-lite distros have EXTRA_IMAGE_FEATURES i.e. "graphics"
and "multimedia" which control the inclusion of our AMD BSP specific
features i.e. "amd-feature-graphics" and "amd-feature-multimedia".
This removes mentor specific "graphics" & "multimedia" feature configs
such that now we leave our AMD BSP specific features to be enabled by
the machines themselves in their corresponding conf/machine/<bsp>.conf
files. But the feature packages will be enabled conditionally in the
amd-features.inc file depending on the availability of "x11-base" in
the IMAGE_FEATURES for graphics pkgs and "alsa" in COMBINED_FEATURES
for the multimedia pkgs.
Also, MEL structure required "x11" in MACHINE_FEATURES for targets that
required X11/GUI based images otherwise x11 is dropped from the distro.
This also removes that config as x11 is not actually a machine feature.
See following commits for background:
2dd6c485fda57ef86ce7d48536ca4d0b42cebd3e
5d05eb929bb27c30325471c6f01812ec0f125c72
63cbf8208d70f49fe46f3e938df3ee04455b7fed
fca5be162809ffc1c3615dc629ada323a5aeb51a
36b85e0aec98955257826598e43bc9b81d75fc9f
7f28a188039e29455d5f58213cd3fc875412c4bc
8c46b32fb1225fe5aa015be0c958ff97ec2d7e56
We are doing this in preparation for yocto based warrior branch.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This removes the mentor swupdate bits in preparation for the
yocto based warrior branch
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This makes bitbake to pick up our layer-specific bb files as well
(as opposed to the previous setting of picking only bbappends) which
are only applied when that layer is included in our configuration.
This change is required for common/dpdk/recipes-entended/dpdk recipe.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The security utils component clamav requires LLVM in a
similar manner like mesa so set the version that is in
use through our layer.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We know that multiple components depend on LLVM in a
way where they specify specific LLVM versions. We should
list all such through the conf fragment so they are
consolidated in a single place and we can identify
what needs to be changed/validated as LLVM's version
moves.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This works around a MEL bug and should be reverted
once the proper fix is in.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The update image generation mechanism in swupdate configuration
has changed and we no longer support swupdate specific
IMAGE_FSTYPES so drop these otherwise we'll get a build time
error.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
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>
|
|
This specifies the supported MEL IOT_PACKAGES for AMD BSPs as
required by mel-iot layer.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
While creating the .swu through MEL's swupdate classes the
contents of IMAGE_BOOT_FILES are processed in order to collect
all the artifacts. While our BSPs produce a live image
containing the rootfs as a loop device in the boot partition.
This creates a circular dependency where the do_image_ext4
starts depending on itself. Fix this by forcing swupdate classes
to not include these boot files.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This enables swupdate support for the AMD platforms by
providing swupdate as its machine features depending on
the available layers. Also, fixes a few variables required
by MEL's swupdate implementation.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Minor fixes
|
|
Not using immediate expansion causes circular dependencies in
some cases so avoid such issues while depending on
EXTRA_IMAGE_FEATURES.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We do not support legacy boots so using syslinux
does not make any sense at the moment and dropping
such metadata would allow easier maintenance.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This reverts commit 570b7302369a337111cb247cebe19e0ec0e47ccb as it is
fixed in meta-mentor->sumo: 922ef38be26e22b98a15388f66fa0d2770d50cc0
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
MEL adds vmlinux to KERNEL_IMAGETYPES which ends up in the rootfs of
the image being built where it is not needed by us, and as a
side-effect, it results in increasing the size of the image by a
considerable amount. Therefore we do this change, and we'll remove
it from here once fixed in MEL.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This drops hddimg support as the functionality offered by this is
also available through the wic image "amd-usbimage.wks" which is
enabled as a default wic image.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
This adds support for wic images for AMD BSPs by adding "wic" to
IMAGE_FSTYPES.
This commit also creates a "amd-usbimage.wks" file as a default wic
image for AMD BSPs, which uses the bootimg-partition wic source plugin
to create a bootable image.
The contents of this image can be set via IMAGE_BOOT_FILES variable.
This commit populates the image with the files same as in hddimg,
therefore supports both grub EFI boot and syslinux legacy boot.
The IMAGE_BOOT_FILES variable can be overridden to support any
bootloader such as: systemd, or any other files that are required
to be deployed into the wic image can be added here.
This resulting image can be flashed on a USB, and supports both
"boot" and "install" options in the bootloader menu.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
IMAGE_FSTYPES "live" is enabled by default in oe-core which is
responsible for building live images i.e. "iso" & "hddimg". We
need to specify which ones to build and which not using NOISO
and NOHDD vars because NOISO = "1" by default, so "iso" doesn't get
built even if specified explicitly (See commit c787dcd in oe-core).
This commit sets the standard NOISO and NOHDD vars as well for
"hddimg" and "iso" support, while keeping in consideration the
Toaster support as Toaster build artifacts collection mechanism
depends on the IMAGE_FSTYPES variable to specify the image types
explicitly (See commit a5b1aa4).
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The x11 machine feature is now only broadcasted when
user is looking for graphics through EXTRA_IMAGE_FEATURES.
Additionally refine the feature packages in a way such that
a subset of multimedia can be used even when graphics is not
included as a feature.
Signed-off-by: Awais Belal <awais_belal@mentor.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>
|
|
This is now being handled through MEL's config and package
handling is done through features so there's no need of the
setting anymore.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
MEL specifically provides additional components under the
multimedia feature which we need to support here.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
amd-misc-pkgs (previously named as amd-common-pkgs) is intended for:
* Platform Specific Packages
* Common Packages to be added to all machines
* ...and others that may not fall into any feature category, etc.
Also added var AMD_PLATFORM_SPECIFIC_PKGS for any platform specific
misc pkgs etc.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
The multimedia feature is not a common feature and should
only be deployed on supporting platforms. For now, we'll
install these for GPU enabled targets.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The new MEL structure requires x11 in machine configurations
for targets that require X11/GUI based images otherwise x11
is dropped from the distro.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Graphics components to depend on "IMAGE_FEATURES" > "x11-base"
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
"gstreamer1.0-meta-x11-base" to depend on "IMAGE_FEATURES" > "x11-base"
"gstreamer1.0-meta-audio" to depend on "IMAGE_FEATURES" > "tools-audio"
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
defaults to no package included
snowyowl adds its own pkgs
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
|
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@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>
|
|
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>
|
|
|
|
With dbg-pkgs added to EXTRA_IMAGE_FEATURES, build fails at do_bootimg with
an error that ROOTFS_SIZE exceeds 4GB.
Post install scripts and the package management system use disk space inside
an overhead area (which defaults to "1.3"). We will reduce it to 1.1 to
allow build with "dbg-pkgs". Otherwise ROOTFS_SIZE exceeds 4GB.
(Not possible for FAT fs used for HDDIMG)
where:
ROOTFS_SIZE = (actual-rootfs-dir-size * overhead-factor) + rootfs-extra-space
The following can be used to add extra available space in rootfs as required:
IMAGE_ROOTFS_EXTRA_SPACE_append = " + <size-in-kilobytes>"
Also, when using the above variable to add extra space, it may cause an error
similar to this:
The initramfs size 294088(K) overrides INITRAMFS_MAXSIZE: 131072(K)
You can set INITRAMFS_MAXSIZE a larger value. Usually, it should
be less than 1/2 of ram size, or you may fail to boot it.
You may need to adjust INITRAMFS_MAXSIZE variable to fix that, or as a
workaround, you could set it to an empty string, to avoid such error, as:
INITRAMFS_MAXSIZE = ""
Issue: INTAMDDET-2285
Signed-off-by: Arsalan-Awan <Arsalan_Awan@mentor.com>
|
|
Upstream now uses a git based recipe for llvm which
is currently providing llvm5.0 so drop v3.9 and
move to git based recipe for latest updates.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
Arsalan H. Awan
Awais Belal
Wade Farnsworth