xserver merge requestshttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests2020-12-01T16:25:19Zhttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/564Backport !562 to server-1.20-branch2020-12-01T16:25:19ZMatt TurnerBackport !562 to server-1.20-branchJust cherry-picks the patches from !562 to the 1.20 branch.Just cherry-picks the patches from !562 to the 1.20 branch.1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/563xserver 1.20.102020-12-01T17:18:54ZMatt Turnerxserver 1.20.10Signed-off-by: Matt Turner <mattst88@gmail.com>Signed-off-by: Matt Turner <mattst88@gmail.com>1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/560Backporting fixes for 1.20.102020-12-01T15:56:38ZMichel DänzerBackporting fixes for 1.20.101.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/549present/wnmd: Translate update region to screen space2020-12-01T10:31:33ZMichel Dänzerpresent/wnmd: Translate update region to screen spaceThe region as passed in is in the source pixmap's coordinate space, so
intersecting it with the clipList (which is in screen space) resulted in
disappointment.
Fixes Firefox hamburger menu.
Reported-by: Robert Mader <robert.mader@poste...The region as passed in is in the source pixmap's coordinate space, so
intersecting it with the clipList (which is in screen space) resulted in
disappointment.
Fixes Firefox hamburger menu.
Reported-by: Robert Mader <robert.mader@posteo.de>
Tested-by: Robert Mader <robert.mader@posteo.de>1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/542[backports for 1.20] Backports !535, !538 and !540 to xorg/xserver:server-1.2...2020-11-09T10:44:27ZOlivier Fourdan[backports for 1.20] Backports !535, !538 and !540 to xorg/xserver:server-1.20-branchSSIASSIA1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/539Backport glamor pixmap export devKind fix to 1.202020-11-04T19:42:47ZAaron Plattneraplattner@nvidia.comBackport glamor pixmap export devKind fix to 1.20When making a pixmap exportable, glamor will currently create a temporary
exported pixmap backed by a GBM bo, with the devKind updated to the stride of
the bo. However, when the backing of the exported pixmap is swapped into the
original...When making a pixmap exportable, glamor will currently create a temporary
exported pixmap backed by a GBM bo, with the devKind updated to the stride of
the bo. However, when the backing of the exported pixmap is swapped into the
original, the devKind of the original is not updated.
Some GBM bos may get implicitly padded, in which case the devKind of the pixmap
will not match the stride of the backing bo. For example, an 800x600 pixmap will
have a devKind of 3200, but the bo's stride will be 3328. This can cause
corruption with PRIME, when the sink uses the wrong stride to display the shared
pixmap.
This commit changes glamor_make_pixmap_exportable() to update the devKind of the
original pixmap after it swaps exported pixmap's backing into it, keeping
everything consistent.
Fixes issue #1018.
Signed-off-by: Alex Goins <agoins@nvidia.com>
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
(cherry picked from commit 7a7e55c5c1d6461a9f4d9a4e0129c1c6e1fd3d66)1.20.10Aaron Plattneraplattner@nvidia.comAaron Plattneraplattner@nvidia.comhttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/526os: Fix instruction pointer written in xorg_backtrace2020-11-02T13:02:01ZBernhard Übelackeros: Fix instruction pointer written in xorg_backtraceThe address retrieved in "pip.start_ip" is not necessarily the same
address as unw_get_proc_name finds as nearest symbol and returns in "off".
Therefore using "pip.start_ip + off" is not reliable, at least
visible in the binaries from th...The address retrieved in "pip.start_ip" is not necessarily the same
address as unw_get_proc_name finds as nearest symbol and returns in "off".
Therefore using "pip.start_ip + off" is not reliable, at least
visible in the binaries from the Debian repository.
Bug-Debian: https://bugs.debian.org/971088
Signed-off-by: Bernhard Übelacker <bernhardu@mailbox.org>1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/518Backport fixes from master for 1.20.102020-10-01T08:35:23ZOlivier FourdanBackport fixes from master for 1.20.10Assorted backport(s) for the stable branch.Assorted backport(s) for the stable branch.1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/5131.20 backport of !4942020-10-08T08:43:14ZMichel Dänzer1.20 backport of !494To fix black seams / a 1-frame delay with windowed apps using the `Present` extension.
/cc @romangg @ofourdanTo fix black seams / a 1-frame delay with windowed apps using the `Present` extension.
/cc @romangg @ofourdan1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/508[server-1.20-branch] Revert xorg/xserver!4872021-06-23T15:44:17ZOlivier Fourdan[server-1.20-branch] Revert xorg/xserver!487xorg/xserver!487 is causing a regression in the stable branch (see xorg/xserver#1068) and prevents Xorg to start on some hardware.
That does not seem to be related to commit 249a12c5 because there is no `ID_PATH` in the udev export. Yet...xorg/xserver!487 is causing a regression in the stable branch (see xorg/xserver#1068) and prevents Xorg to start on some hardware.
That does not seem to be related to commit 249a12c5 because there is no `ID_PATH` in the udev export. Yet that commit depends on two other dependent changes (commit 5c96eb5f and commit 74b7427c) which are more likely the cause of the issue.
Revert the 3 commits from xorg/xserver!487 to fix the regression until the issues is fixed in master.
CC: @daenzer, @ajax, @airlied, @chenhuacai1.20.10https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/502Backported fixes for 1.20.102020-09-30T15:16:23ZMichel DänzerBackported fixes for 1.20.101.20.10