lp://staging/~thopiekar/arm-mali/xf86-video-fbturbo

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

198. By Siarhei Siamashka on 2015-10-06

Merge pull request #45 from jacmet/drop-dri2-include

sunxi_x_g2d: drop unused dri2 include

197. By Jerome Oufella <email address hidden> on 2015-03-05

sunxi: probe both screen layers at disp probing

Some boards use an inverted screen layer configuration, making the
original code unable to enable disp layers functionality properly.

This commit adds a fallback mechanism to the actual disp probing
sequence, allowing those cases to be properly handled.

Signed-off-by: Jérôme Oufella <email address hidden>

196. By Siarhei Siamashka on 2014-09-20

Check if the kernel framebuffer driver returns errors on bad ioctls

When probing for the copyarea ioctl, we want to be sure that the
kernel just does not return 0 (success) for any unsupported ioctls.
The rockchip vendor kernels have been reported to have this issue.

In the case if the support for the Raspberry Pi specific copyarea
ioctl was detected by mistake, moving windows or scrolling was
broken.

Signed-off-by: Siarhei Siamashka <email address hidden>

195. By Siarhei Siamashka on 2014-03-31

vdpau: Report DRI2 VDPAU driver name as 'sunxi' on Allwinner hardware

Try to load the 'sunxi_cedar_mod' kernel module. And if it loads
successfully, then report the DRI2 VDPAU name as 'sunxi'. This allows to
use libvdpau-sunxi without setting the VDPAU_DRIVER environment variable.

Signed-off-by: Siarhei Siamashka <email address hidden>

194. By Siarhei Siamashka on 2014-03-29

Don't use hardware cursor for rotated desktop

Fixes https://github.com/ssvb/xf86-video-fbturbo/issues/30

Signed-off-by: Siarhei Siamashka <email address hidden>

193. By Siarhei Siamashka on 2014-01-12

Post-release version bump to 0.5.1

Signed-off-by: Siarhei Siamashka <email address hidden>

192. By Siarhei Siamashka on 2014-01-12

Pre-release version bump to 0.4.0

It makes sense to make a formal release. Providing the
pre-generated 'configure' script should make it less
likely for people to mess with autotools and encounter
troubles:

    https://github.com/ssvb/xf86-video-fbturbo/issues/28
    https://github.com/ssvb/xf86-video-fbturbo/issues/25

Also it's likely that this particular xf86-video-fbturbo
git master snapshot was used in:

    http://www.raspberrypi.org/archives/5580

Signed-off-by: Siarhei Siamashka <email address hidden>

191. By Siarhei Siamashka on 2014-01-12

autotools: add missing headers to Makefile.am to fix 'make distcheck'

Signed-off-by: Siarhei Siamashka <email address hidden>

190. By Siarhei Siamashka on 2013-12-09

mali: detect and workaround mismatch between back and front buffers

After window creation or resize, the mali blob on the client side
requests two dri2 buffers (for back and front) from the ddx. The
problem is that the 'swap' and 'get_buffer' operations are executed
out of order relative to each other and we may have different
possible patterns of dri2 communication:

1. swap swap swap swap get_buffer swap get_buffer swap swap ...
2. swap swap swap get_buffer swap swap get_buffer swap swap ...

A major annoyance is that both mali blob on the client side and
the ddx driver in xserver need have the same idea about which one
of there two buffers goes to front and which goes to back. Older
commit https://github.com/ssvb/xf86-video-fbturbo/commit/30b4ca27d1c4
tried to address this problem in a mostly empirical way and managed
to solve it at least for the synthetic test gles-rgb-cycle-demo and
for most of the real programs (such as Qt5 applications, etc.)

However appears that this heuristics is not 100% reliable in all
cases. The Extreme Tux Racer game run in glshim manages to trigger
the back and front buffers mismatch. Which manifests itself as
erratic penguin movement.

This patch adds a special check, which now randomly samples certain
bytes from the dri2 buffers to see which one of them has been
modified by the client application between buffer swaps. If we see
that the rendering actually happens to the front buffer instead of
the back buffer, then we just change the roles of these buffers.

Signed-off-by: Siarhei Siamashka <email address hidden>

189. By Daniel Drake <email address hidden> on 2013-11-15

Auto-detect mali DRI device path

When using exynos_drm, /dev/dri/card0 is now the exynos-drm node, and
/dev/dri/card1 is mali.

Instead of hardcoding mali at card0, use libdrm to automatically
provide the correct device node path.

Signed-off-by: Daniel Drake <email address hidden>