Age | Commit message (Collapse) | Author |
|
1.9.0 was released in August 2010.
We were already unintentionally relying on things not available in 1.8
for at least a year, and nobody has complained.
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
If we were asked to create a shareable pixmap, it doesn't make sense
to return a pixmap which isn't shareable. Doing so caused trouble down
the line such as a crash with older versions of glamor when trying to
use GLX pixmaps of bpp < 32 via DRI2.
Signed-off-by: JimQu <jim.qu@amd.com>
(ported from amdgpu commit 2fcb7dadd3c71cd405cbbaafc777697538ca9c29)
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
The next commit will call the former from the latter. No functional
change.
Signed-off-by: JimQu <jim.qu@amd.com>
(ported from amdgpu commit 5269a2228bff6023c1a7f3e8534027e1d7addc25)
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
When it's not available, it's safe to call down to the glamor
DestroyPixmap hook instead.
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
It only works when using glamor.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90169
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Its value was always the same as that of the PixmapRec devKind member.
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
When this option is enabled, most pixmaps (including the screen pixmap)
are allocated in system RAM and mostly accessed by the CPU. Changed areas
of the screen pixmap are copied to dedicated per-CRTC scanout pixmaps
regularly, triggered by the vblank interrupt.
v2:
* Set region data pointer to NULL for keeping only the extents
* Move pRegion and pBox local variable declarations closer to their uses
in drmmode_set_mode_major()
|
|
|
|
|
|
The behaviour is the same as when the removed flags were passed in.
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
[ Michel Dänzer: Fixups for glamor ]
Signed-off-by: David Heidelberger <david.heidelberger@ixit.cz>
Signed-off-by: Axel Davy <axel.davy@ens.fr>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
This reverts commit 4b5060f357a3cb248c9359c92c1e9c42ef6434c8.
Further testing shows that disabling the thread is only a moderate win in
some cases, but a much bigger loss in some other cases.
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
Also make this case clear in the log file:
(WW) RADEON(0): EXA not supported, using glamor
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
The pixmap usage hint is not a bitmask in general. The test for
CREATE_PIXMAP_USAGE_SHARED was incorrectly triggering for a glamor internal
usage hint being added in the xserver tree.
Tested-by: Ed Tomlinson <edtoml@gmail.com>
|
|
|
|
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75709
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
|
|
The issues with loading it on demand have been fixed in xserver 1.15.
Inspired by Jérôme Glisse on IRC.
|
|
This creates adaptors using glamor if possible.
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
|
I'm not sure they can handle the shaders properly, especially
only older parts like r300.
This will avoid display corruption problems reported by people
using glamor on older asics by falling back to EXA if they try
and enable glamor.
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
|
|
Those didn't define CREATE_PIXMAP_USAGE_SHARED.
|
|
It can't handle lower depths yet.
Reported-by: Igor Vagulin <igor.vagulin@gmail.com>
|
|
We should now handle its major initialization failure cases gracefully.
Reviewed-by: Jerome Glisse <jglisse@redhat.com>
|
|
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=57200
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Tested-by: Christoph Haag <haagch.christoph@googlemail.com>
Tested-by: linedot <linedot@xcpp.org>
|
|
Trying to initialize glamor in that case crashes.
Reviewed-by: Jerome Glisse <jglisse@redhat.com>
|
|
Fixes rotation with glamor.
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
|
|
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
|
|
Improves performance of non-pageflipped 3D apps on SI.
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
|
|
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
|
|
Defaults to shadowfb. 3D acceleration is available with glamor. 2D
acceleration is disabled until the radeonsi driver can handle glamor's
shaders.
v2: add chip flags (Alex Deucher)
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
|
|
Enable at build time with --enable-glamor and runtime with
Option "AccelMethod" "glamor"
The most notable lack of functionality is XVideo. Use something like VDPAU for
now.
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
|