Age | Commit message (Collapse) | Author |
|
The base version available for libav for jethro onwards
branches is 9.18 so we update accordingly in order to
steer clear of the QA warnings.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Fixes build errors such as:
<build_dir>/tmp/work/dbft3b-poky-linux/xf86-video-ati/2_7.4.0+gitAUTOINC+906a0ec922-r21.1/git/src/drmmode_display.c:795:2:
error: too few arguments to function 'PixmapStartDirtyTracking'
PixmapStartDirtyTracking(ppix, screenpix, 0, 0);
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
BaldEagle, SteppeEagle and AMD Falcon Series are multilib
architectures with the rootfs/tools having lib64 additionally
to /lib. If these platforms are not marked with having multilib
compatibility we run in to issues like:
ERROR: Unable to locate installed libc.so file
(/usr/lib/libc.so). This may mean that your external toolchain
uses a different multi-lib setup than your machine configuration.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
Resolves open Yocto build errors such as:
ERROR: Nothing RPROVIDES 'firmware-wireless' (but
...poky/meta/recipes-core/packagegroups/packagegroup-base.bb
RDEPENDS on or otherwise requires it)
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
MEL provides a subset of firmware from linux-firmware that
have acceptable licensing terms through firmware-wireless
so we use that as it follows the general product rules.
It is done through recommendations so to avoid issues
in open environment.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
The layer priority under meta-amd is currently same (6) for all
layers. Which makes it a little difficult to deterministically
override changes from the layers we inherit from.
We now adjust the priority of all layers so things like
prepend/append can be done a little more deterministically.
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 meta-steppeeagle layer should not affect build meta-data
when it is not intended to be built.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The connman version is handled through mel specific
versioning so no warnings/errors are encountered
in the open builds.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Conflicts:
common/recipes-graphics/mesa/mesa_10.4.4.bbappend
common/recipes-multimedia/gstreamer/gstreamer1.0-omx_git.bbappend
|
|
bitbake reads MACHINEOVERRIDES from left to right, least to most specific. Prepend 'amd:' to
stay compliant.
|
|
Conflicts:
common/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.12-kernel.patch
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
connman version 1.28 is now available which provides quite a few
bug fixes over the 1.25 version. We now move to 1.28 to leverage
the stability.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
A display mode is necessary in order to kick off the VESA driver
through kernel commandline particularly in the legacy boot mode
otherwise the frame buffer device (/dev/fb) is not created and
hence the logo/splash displays fail.
This is safe as X server can further set itself up according to
its own configuration rather than relying on this.
Signed-off-by: Awais Belal <awais_belal@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>
|
|
|
|
This enables the CONFIG_FB_UVESA kernel option which seems to
conflict with CONFIG_FB_EFI or CONFIG_FB_RADEON. Since we don't
need multiple FB options this seems like the simplest fix.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This rather large patch upgrades the AMD Steppe Eagle and
Bald Eagle platforms to the v3.12.34 stable tag.
Additionally it renames the kernel recipe to linux-amd since
it is _not_ a linux-yocto style recipe.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This is in preparation for the upcoming upgrade to the latest
stable kernel v3.12.x version.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Both BaldEagle and SteppeEagle use the same xorg configuration
hence it can be moved to common layer.
Any BSP requiring additional configurations should provide
the conf file through an append as it was done earlier.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The BaldEagle and SteppeEagle layers both simply override the
DRIDRIVERS setting to 'radeon', we can move this to common
layer as it works for both BSPs.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
- Mullins support present in 7.4.0
|
|
intamddet-144
|
|
- Move xf86-video-ati_git.bb to xf86-video-ati.inc and create two versioned recipes to be used
- SteppeEagle: Remove libdrm preferred version
|
|
Moving on to version 2.5.4 of libdrm, the patches for MULLINS
family are already found in the mentioned version so the
append from steppeeagle layer can be safely dropped.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
The common bits for radeon-firmware package are now
moved to amd/common layer. SteppeEagle and BaldEagle layers
now contain platform specific updates only.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Both SteppeEagle and BaldEagle configurations for xserver-xorg
are common, so we now move the appending bb to the amd/common
layer.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The recipes for wdt-load and gpio-load are now part
of the common layer.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
mesa recipe updates are now moved to amd/common layer
with architecture specifications. The BaldEagle and
SteppeEagle layers now only contain var settings for
DRIDRIVERS.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The base recipe for libvdpau is now moved to amd/common.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The main recipe for xf86-video-ati is now provided through
the amd/common layer. The BaldEagle and Steppe Eagle only
provide specifics for platform.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The vdpauinfo package recipe is now moved to amd/common.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The main llvm recipe is now moved to amd/common. The
SteppeEagle layer now contain bits that are specific
to the platform.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The main kernel recipe is now moved to amd/common. The
BaldEagle and SteppeEagle layers now contain kernel bits
that are specific to the platform.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
spirom.h header file should be same for both the test app and the
SPI client driver, since they refer the same IOCTL structure and
to driver directory.
|
|
All the other SDK components under meta-applications are already
shell based. This patch makes SPI test application also shell
based, so that all SDK components now are alike, at least on
the functional level.
|
|
This patch fixes the issue where the kernel thread would
unnecessarily hog the CPU even when there is no actual SPI
transaction happening. The changes now make sure that the
kernel thread waits on a waitqueue until a SPI message is
actually queued into the buffer, thus saving precious CPU
cycles.
Upstream Status: None
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
This is useful when installing onto SATA hard drives
to be able to determine the PARTUUID.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
The libraries installed by for omx-bellagio support are not
expected to be versioned and symlinked. Notably,
the "omxregister-bellagio" app scans for them explicitly using
the ".so" extension. Ensure that only the unversioned versions
are installed in the main package.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Make some changes to the order of the PACKAGE variable to ensure
that the last package in the list is still "mesa". This avoids
issues with the debian.bbclass renaming feature changing the package
names to libxatracker-blah.
Also, put all the debug bits into the main mesa-dbg recipe rather
than creating a separate one.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
If mplayer is included in a custom build this version
of libav is needed.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|