| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
|
|
On images such as console-image or core-image-base where
no x11 or GUI support is available we do not want to deploy
the gst packages so make the inclusion conditional.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
These are required for the dual-boot setup as well where
grub is launched manually for installation.
This reverts commit 37e12862f1886e2fc8f103ce108318c6b0fd4e39.
|
|
We now drop the git based recipe and move to 17.1.1
which builds/boots perfectly for the currently
supported AMD BSPs.
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>
|
|
Upstream has dropped the git based recipe for gstreamer-omx
so we need to adjust accordingly.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
These are installed as needed through the initramfs
bits where these are actually required.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
The recipe naming for different gstreamer components is pretty
well defined upstream, where gstreamer1.0- is used as a
prefix for all components. This is now corrected for our
in house gstreamer vaapi recipe.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
The Toaster build artifacts collection mechanism depends
on the IMAGE_FSTYPES variable to identify if required
build artifacts are present. The Toaster GUI only shows
the build artifacts if they are detected properly.
We now add the required image types explicitly for
AMD BSPs so Toaster shows the build artifacts as
intended.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
Upgraded llvm from 3.7.1 to 3.9.1 for AMD BSPs.
The recipe has been created from scratch taking and
merging changes from meta-oe because there are things
that cannot be overriden through appends or any other
cleaner mechanism. mesa has been adjusted accordingly
as well.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
|
|
This upgrades mesa to 12.0.3 from 11.0.8.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
|
|
This reverts commit cb942be5728da17dcfb51819ef73e4a91981e44c.
|
|
|
|
Update grub and grub-efi
|
|
This enables git based grub recipes to be used
for AMD BSPs.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
If a variable is not defined at all bitbake tends to use
the literal value which causes failures and unintended
settings in various cases. This now uses a very weak
default to cope with this problem.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The xserver changes have been consolidated between
OE-core and meta-oe so the specific setting for
xserver-nodm-init are no longer required.
The SPLASH variable now already defaults to psplash
in MEL configurations so we don't need to set this
either.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
Arsalan H. Awan
Awais Belal
Wade Farnsworth
Drew Moseley
Sanjay R Mehta
Drew Moseley