Age | Commit message (Collapse) | Author |
|
Merge latest bits from release/2014.12
|
|
|
|
mesa-demos: fix deadlock in sharedtex_mt
|
|
This patch fixes a deadlock that occurs between the main
thread and rendering threads of the sharedtex_mt demo.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
The driver registers spirom device on init by using the
spi_new_device call which acquires the chip select pin
through board_info. If the driver does not unregister
this device while exiting the chip select pin never frees
and consequently a second modprobe for the device will
fail with chip select already in use error.
We now keep the device pointer for the device added through
spi_new_device and make an unregister call on the same
on driver's exit.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
MMC devices get auto mounted during installation without
this and cause a failure while formatting the device.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
amd-spi: unregister spirom device on exit
|
|
The driver registers spirom device on init by using the
spi_new_device call which acquires the chip select pin
through board_info. If the driver does not unregister
this device while exiting the chip select pin never frees
and consequently a second modprobe for the device will
fail with chip select already in use error.
We now keep the device pointer for the device added through
spi_new_device and make an unregister call on the same
on driver's exit.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
external-sourcery-toolchain: workaround erroneous libdir pointing
|
|
Merge from release/2014.12 into dizzy
|
|
The debug agent in CB wrongly points to /usr/lib6464 rather
than to /usr/lib64 to pick up the gdbserver binary. This
makes any debug session fail due to not finding the
binary.
We work around the issue by creating a symlink from /usr/lib6464
to /usr/lib64.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
|
|
xserver-xf86-config: use SWcursor for amdfalconx86
|
|
qtwebkit-examples: fix ADE creation
|
|
vdpauinfo: Lockdown SRCREV
|
|
ADEs are generated by picking up -dev subpackages of all the
packages included in build. In case of qtwebkit-examples, the
way qt5 submodules are populated the actual generated package
of qtwebkit-examples is qtwebkit-examples-examples. When
ADE creation picks up qtwebkit-examples-dev it fails to
find the qtwebkit-examples package which is a dependency
for the -dev package.
This patch allows generation of the qtwebkit-examples
package to satisfy this dependency by allowing this
empty package to be built.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Explicitly use a SRCREV variable rather than a tag specifier
in the SRC_URI to avoid errors when building without a network
connection in the resultant installed build.
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
|
|
When HDMI goes to power save mode and mouse movement
or key press will bring it back to normal operation
but the mouse cursor isn't shown.
We now use the SWcursor which forces software to
draw the cursor rather than hardware to cope with
this issue.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
meta-amdfalconx86: enable AMD eMMC and GPIO SDK support
|
|
amd: Conditionalize firmware-wireless on MEL based distros.
|
|
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>
|
|
The AMD GPIO driver is now in-kernel. So the out-of-tree GPIO
module is no longer required. The gpio-amd.conf file was used
to pass module load parameters to the GPIO driver which should
now be removed as well.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
baldeagle/steppeeagle: add firmware-wireless
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.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>
|
|
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>
|
|
2014.12
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
firmware-wireless: fix QA warning
|
|
Fix for QA warning
"WARNING: QA Issue: FILES variable for package firmware-wireless
contains '//' which is invalid. Attempting to fix this but
you should correct the metadata."
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Fix WiFi support
|
|
The current firmware-wireless recipe deploys bins to
base_libdir/firmware (/lib64/firmware in our case) whereas
the generic approach is to deploy these to /lib/firmware
directory so we override as required.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The detection and enumeration of generic WiFi devices
is currently not available due to lack of the driver
support.
We now enable some generic drivers to cover for these
devices.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Some devices require firmware to be able to get
detected and work correctly.
We now enable the available firmware packages to
be deployed on the target.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
mesa: drop dependency on wayland
|
|
Drop an un-necessary dependency on wayland which tends to
pull in wayland whereas we are using X. Also, the correct
way of doing this would be through adding wayland to
PACKAGECONFIG.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
2014.12
|
|
The AMD GPIO driver conflicts with the in-kernel GPIO driver
needed by I2S. This commit removes the AMD GPIO driver for now.
The GPIO application will later be modified to use the in-kernel
GPIO driver.
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
Signed-off-by: Arindam Nath <arindam.nath@amd.com>
|
|
R8168: migrate to kernel sources
|
|
We are now utilizing the in-tree driver for r8168
so the external module is not needed anymore.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
We now enable the in-tree r8168 driver and disable
the externally built module. This gives us the ability
to boot over NFS.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
The NICs on AMD Falcon family platforms utilize the
r8168 driver from realtek and fail to perform correctly
with the built-in r8169 driver.
We now merge the r8168 driver source in the kernel so
we are able to use it as built-in rather than an
external module.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
|
|
Merge from release/2014.12 into dizzy
|
|
|