| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
The Mentor Embedded splash screen has a higher resolution
than what we get with vga=802 (800x600) so it comes out
clipped. Also the vga=xxx parameter usage has been
deprecated under grub2 and cannot be used to set a
particular resolution so it picks up a default in most
cases.
We now use vga=803 (1024x768) only for handling the
syslinux environment and set gfxpayload accordingly
to cope for the grub2 scenarios.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The machine configuration now includes a config fragment
that can be provided through customer layers. This will
help in situations where a variable can only be touched
through conf files rather than recipes one such example is
the SERIAL_CONSOLES variable.
Also pick up APPEND_ADDITIONAL which can be passed through
the same customer layer for flexibility.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This was handled differently earlier in
b1676a652df606cc35ce2642f35d72b910fb0dd4 for which the
patch was dropped later during kernel upgrade. This is
a better way of solving the same problem.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
As a best practise the serial consoles should be
provided earlier on the kernel command line than
the vga consoles because the last console is used
for taking user input and is mapped to /dev/console.
Using it differently can break things at places
where conflicting/incorrect serial drivers can
generate a kernel panic in such a scenario.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
linux-yocto: RT, update for SE/BE and general fixes.
|
|
Currently the default used by MEL BSPs is plymouth
however it does not function appropriately on AMD
platforms.
We now switch to using psplash which seems to be the
preffered one going forward.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This commit does a few things which cannot be separated easily
so it cannot be split in to separate commits.
* Drops all 4.1 kernel bits.
* Moves all common patches from meta-amdfalconx86 to common.
* Moves SE/BE builds to 4.4 kernel.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
These packages have been removed.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
With the new layer priority handling introduced into
MEL we have to explicitly set version for xserver-nodm-init.
So we now conslidate both xserver-nodm-init and xserver-common
to be picked up from meta-oe. Once the versions found in
OE-core and meta-oe are merged this should be dropped.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
This consolidates the common configurations between the
different machines and move them to common from where
these are used through an include to make things more
maintainable.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
Awais Belal
Arsalan H. Awan
Drew Moseley
Sanjay R Mehta
Drew Moseley
Michael