summaryrefslogtreecommitdiff
path: root/configure.ac
AgeCommit message (Collapse)AuthorFilesLines
2017-09-08Bump version for 1.4.0 releasexf86-video-amdgpu-1.4.0Michel Dänzer1-1/+1
2017-08-31Require xserver >= 1.13Michel Dänzer1-7/+1
xserver 1.13.0 was released on September 6th, 2012, almost 5 years ago. This allows cleaning up a bunch of backwards compatibility code. (Ported from radeon commit 5cdd334b3402c2431deb3a87a8d04ef590da53ee) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2017-08-22modesetting: re-set the crtc's mode when link-status goes BADMartin Peres1-1/+1
Despite all the careful planning of the kernel, a link may become insufficient to handle the currently-set mode. At this point, the kernel should mark this particular configuration as being broken and potentially prune the mode before setting the offending connector's link-status to BAD and send the userspace a hotplug event. This may happen right after a modeset or later on. Upon receiving a hot-plug event, we iterate through the connectors to re-apply the currently-set mode on all the connectors that have a link-status property set to BAD. The kernel may be able to get the link to work by dropping to using a lower link bpp (with the same display bpp). However, the modeset may fail if the kernel has pruned the mode, so to make users aware of this problem a warning is outputed in the logs to warn about having a potentially-black display. This patch does not modify the current behaviour of always propagating the events to the randr clients. This allows desktop environments to re-probe the connectors and select a new resolution based on the new (currated) mode list if a mode disapeared. This behaviour is expected in order to pass the Display Port compliance tests. (Ported from xserver commit bcee1b76aa0db8525b491485e90b8740763d7de6) [ Michel: Bump libdrm dependency to >= 2.4.78 for DRM_MODE_LINK_STATUS_BAD ] (Ported from radeon commit 0472a605e0ec8fec1892bbc3a84698b7ef9c5296) Acked-by: Harry Wentland <harry.wentland@amd.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2017-07-27Add AC_CONFIG_MACRO_DIRS([m4]) to configure.acMichel Dänzer1-0/+1
Suggested by one of the tools called by autoreconf. Acked-by: Alex Deucher <alexander.deucher@amd.com>
2017-05-24Update URLsMichel Dänzer1-1/+1
* Point to the amd-gfx mailing list * Specify the component in all bugzilla URLs * Use https:// for all HTML URLs (Ported from radeon commit d80d01a73c2eaba2e3649b7bc0a3541b3ff782f6) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2017-03-23Post-release version bumpMichel Dänzer1-1/+1
2017-03-16Bump version for 1.3.0 releasexf86-video-amdgpu-1.3.0Michel Dänzer1-1/+1
2017-03-07glamor: Use glamor_finish when availableMichel Dänzer1-2/+7
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2017-03-07Use local implementation of RegionDuplicate for older xserverMichel Dänzer1-0/+6
It was only added in xserver 1.15. Fixes build against older xserver. Reported-by: Pali Rohár <pali.rohar@gmail.com> (Ported from radeon commit 80cc892ee1ce54fad3cb7dd11bd9df18c359136f) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-11-28Make libdrm >= 2.4.72 requirement explicitMichel Dänzer1-1/+1
And drop compatibility code for older versions. Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-11-21Stop using AMDGPU(Unique)ChipsetsMichel Dänzer1-1/+1
Use libdrm_amdgpu's amdgpu_get_marketing_name for the chipset name, or "Unknown AMD Radeon GPU" as a fallback. v2: Require libdrm_amdgpu >= 2.4.72 for amdgpu_get_marketing_name Reviewed-by: Alex Deucher <alexander.deucher@amd.com> (v1)
2016-11-21Post-release version bumpMichel Dänzer1-1/+1
2016-11-17Bump version for 1.2.0 releasexf86-video-amdgpu-1.2.0Michel Dänzer1-1/+1
2016-11-02Require xserver 1.10 or newerMichel Dänzer1-1/+1
1.10.0 was released in February 2011. We've been accidentally requiring 1.10 or newer since c7d27c94cb65 ("Keep track of damage event related flushes per-client"). (Ported from radeon commit 5df36de39952c3a26cb2fbc125f298139a9dd5bc) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-10-25Sayōnara, AM_MAINTAINER_MODE!Michel Dänzer1-2/+0
If --enable-maintainer-mode got lost from config.status for any reason, builds would fail in mysterious ways after changing between different Git commits. There are more reasons for dropping it in the automake manual: https://www.gnu.org/software/automake/manual/html_node/maintainer_002dmode.html I'm not aware of any reason why --disable-maintainer-mode would ever be useful with this project. Reviewed-by: Alex Deucher <alexander.deucher@amd.com> (Cherry picked from radeon commit 49cf3b5032a7ce40afe514b7092440e3e19e05aa)
2016-09-20Untangle HAS_XORG_CONF_DIR / --with-xorg-conf-dir lines in configure.acMichel Dänzer1-2/+3
$sysconfigdir used to be part of the default --with-xorg-conf-dir value, but it no longer is. Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-09-16Fix handling of configure option --with-xorg-conf-dirMichel Dänzer1-3/+4
There were two problems: I accidentally changed the variable name in the AC_ARG_WITH stanza from configdir to xorgconfigdir, so specifying --with-xorg-conf-dir wouldn't work correctly. Fix this back to configdir. If neither --with-xorg-conf-dir nor --prefix is specified on the command line, the $prefix variable doesn't contain "/usr/local" (the default prefix) yet at this point but "NONE". So make install would attempt to install 10-amdgpu.conf in ${DESTDIR}NONE/share/X11/xorg.conf.d/ . Fix this by leaving ${prefix} verbatim in the default value, to be resolved by make. Also print the configdir value along with the values of other similar configuration variables. Reported-by: Timo Aaltonen <tjaalton@debian.org> Reviewed-by: Julien Cristau <jcristau@debian.org>
2016-09-14Use --with-xorg-conf-dir=$prefix/share/X11/xorg.conf.d by defaultMichel Dänzer1-3/+3
We were using the result of `pkg-config --variable=sysconfigdir xorg-server` before, which may not be inside $prefix, so make install might fail for 10-amdgpu.conf . Fixes make distcheck in that case, and possibly also 10-amdgpu.conf seemingly missing from some distribution packages. This matches what some (though not all) input drivers are doing for their xorg.conf.d snippets.
2016-04-11Post 1.1.0 release version bumpMichel Dänzer1-1/+1
2016-04-07Bump version for 1.1.0 releasexf86-video-amdgpu-1.1.0Michel Dänzer1-1/+1
2016-03-25Revert "Use render node for DRI3 if available"Michel Dänzer1-1/+1
This reverts commit ea558e645786b08d75307716036045170e97b43e. It broke VDPAU<->GL interop with DRI3 enabled, because the Gallium VDPAU code doesn't support DRI3 yet. We can consider re-enabling this once there is a Mesa release where the Gallium VDPAU code supports DRI3. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94675 Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-03-25Require xserver 1.9 or newerMichel Dänzer1-1/+1
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. (Ported from radeon commit e592f32f8b5f5873fcc18b10a69dd5e4ccf11073) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2016-03-25Check for xf86CursorResetCursorMichel Dänzer1-0/+6
If it's available, Xorg calls it on each mode configuration change. It does what xf86_reload_cursors does (and more), so we don't need to call the latter anymore. (Ported from radeon commit d670c5c9851b4eff21c845d26c7d7e4eb5ee0fa9) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-11-20Use render node for DRI3 if availableJammy Zhou1-1/+1
Signed-off-by: Jammy Zhou <Jammy.Zhou@amd.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
2015-11-20glamor: Deal with glamor_egl_destroy_textured_pixmap being removedMichel Dänzer1-0/+6
When it's not available, it's safe to call down to the glamor DestroyPixmap hook instead. (ported from radeon commit 10b7c3def58bb34acc38f076bc230e25b454ab79) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-11-19Post 1.0.0 release version bumpMichel Dänzer1-1/+1
2015-11-19Bump version for 1.0.0 releasexf86-video-amdgpu-1.0.0Michel Dänzer1-1/+1
2015-11-19Do not link amdgpu_drv.so against libpciaccessEmil Velikov1-3/+0
Not used directly. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com> (ported from radeon commit fcb32231a38f9461d12720cbf72f63502197a711) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-08-11glamor: Add amdgpu_glamor_finish to wait for glamor rendering to finishMichel Dänzer1-0/+2
This is a bit sneaky, because it calls glFinish directly from the driver, but it seems to work fine. Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-06-15glamor: Add Option "ShadowPrimary"Michel Dänzer1-0/+10
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. (Cherry picked from radeon commits ae92d1765fa370a8d94c2856ad6c45d273ec3c69 and 1af044d7eee211fd4b248c236280274a68334da5) [ Michel Dänzer: Additional adjustements for the amdgpu driver ] Signed-off-by: Darren Powell <darren.powell@amd.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-06-08Add DRI3 supportMichel Dänzer1-0/+4
Must be enabled with Option "DRI3" in xorg.conf. (Cherry picked from radeon commits 64e1e4dbdd3caee6f5d8f6b6c094b4533fa94953, 694e04720b886060fe3eefdce59741f218c8269f, f940fd741b15f03393037c5bb904cd74f012de9d, fcd37f65f485291084c174666bd605e215bf1398, 4b0997e56dec0053cb2cb793e0f4ae35055ff7e6, f68d9b5ba0c91a725b5eec9386c61bea8824c299 and 98fb4199e63fedd4607cddee64bf602d6398df81) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-06-08Add support for the Present extensionMichel Dänzer1-0/+6
(Cherry picked from radeon commits 3c65fb849e1ba9fb6454bcaa55b696548902f3fc, 694e04720b886060fe3eefdce59741f218c8269f, e3be8b0a8cf484ff16597413a6172788178e80c8, 80eede245d1eda27eaba108b0761a24bfd69aff6 and 5f82a720374c9c1caebb42bfbeea1f0cf8847d28) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-06-08Add support for SYNC extension fencesMichel Dänzer1-0/+6
(Cherry picked from radeon commits 8fc9a241ab59ffbcdc178d6415332c88a54e85fe, af1862a37570fa512a525ab47d72b30400d2e2d6, aa7825eb29cdf6ac9d7b28ad18186807ff384687, af6076241c0d322b295a4e898407ae2472bd8eb4 and d64a13ebe0ecd241ee3260dbffd8f4a01e254183) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-06-02Require at least xserver 1.8Michel Dänzer1-13/+6
So we can rely on the list.h header. xserver 1.8 was released in April 2010. (Cherry picked from radeon commit 7388d0b6c54b9d536fdb161e3aa61b326627b939) Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-05-29Check GBM_BO_USE_LINEAR correctly v2Jammy Zhou1-0/+5
v2: remove the check for gbm.h Signed-off-by: Jammy Zhou <Jammy.Zhou@amd.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com> [v1]
2015-05-15glamor: Deal with glamor_glyphs_init being removed from xserverMichel Dänzer1-0/+6
Port of radeon commit 818c180c8932233b214a35ba0647af82f7bcec3d.
2015-05-13Link against libgbmMichel Dänzer1-0/+1
Fixes unresolved symbol "gbm_create_device". Reported-and-Tested-by: Brian Paterni <bpaterni@gmail.com>
2015-04-24Add 10-amdgpu.conf xorg.conf.d snippetMichel Dänzer1-0/+14
This instructs Xorg >= 1.16 to try loading the amdgpu driver for devices managed by the amdgpu kernel driver. Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
2015-04-20amdgpu: add the xf86-video-amdgpu driverAlex Deucher1-0/+234
This adds the new xf86-video-amdgpu driver for newer AMD GPUs. Signed-off-by: Alex Deucher <alexander.deucher@amd.com>