lp:xserver-xorg-driver-ati

Created by James Westby on 2009-12-16 and last modified on 2019-01-09
Get this branch:
bzr branch lp:xserver-xorg-driver-ati

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
xserver-xorg-driver-ati
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://anongit.freedesktop.org/xorg/driver/xf86-video-ati.

The next import is scheduled to run in 51 minutes.

Last successful import was 5 hours ago.

Import started 5 hours ago on izar and finished 5 hours ago taking 15 seconds — see the log
Import started 11 hours ago on alnitak and finished 11 hours ago taking 20 seconds — see the log
Import started 17 hours ago on izar and finished 17 hours ago taking 20 seconds — see the log
Import started 23 hours ago on izar and finished 23 hours ago taking 20 seconds — see the log
Import started on 2019-01-19 on izar and finished on 2019-01-19 taking 15 seconds — see the log
Import started on 2019-01-19 on alnitak and finished on 2019-01-19 taking 20 seconds — see the log
Import started on 2019-01-19 on izar and finished on 2019-01-19 taking 20 seconds — see the log
Import started on 2019-01-18 on alnitak and finished on 2019-01-18 taking 20 seconds — see the log
Import started on 2019-01-18 on alnitak and finished on 2019-01-18 taking 20 seconds — see the log
Import started on 2019-01-18 on izar and finished on 2019-01-18 taking 15 seconds — see the log

Recent revisions

3063. By Michel Dänzer <email address hidden> on 2019-01-09

Only call drmmode_validate_leases if RandR is enabled

It would crash if RandR is disabled, e.g. because Xinerama is enabled.

Bugzilla: https://bugs.freedesktop.org/109230
Reviewed-by: Alex Deucher <email address hidden>

3062. By Michel Dänzer <email address hidden> on 2019-01-09

Only call drmmode_uevent_init if RandR is enabled

There's no point in listening for hotplug events if RandR is disabled,
as there's no other mechanism for them to be propagated. We were already
mostly ignoring them in that case.

Inspired by
https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/commit/1a489142c8e6a4828348cc9afbd0f430d3b1e2d8
(via https://bugs.freedesktop.org/109230#c11).
Reviewed-by: Alex Deucher <email address hidden>

3061. By Michel Dänzer <email address hidden> on 2018-12-28

Use two HW cursor buffers per CRTC

Switch to the other buffer when xf86_config->cursor changes. Avoids
these issues possible when re-using the same buffer:

* The HW may intermittently display a mix of the old and new cursor
  images.
* If the hotspot changes, the HW may intermittently display the new
  cursor image at the location corresponding to the old image's hotspot.

Bugzilla: https://bugs.freedesktop.org/108832
(Ported from amdgpu commit 0d60233d26ec70d4e1faa343b438e33829c6d5e4)

3060. By Michel Dänzer <email address hidden> on 2018-12-28

Update cursor position in drmmode_show_cursor if hotspot changed

The cursor position is updated to be consistent with the new hotspot in
the same ioctl call.

(Ported from amdgpu commit b04697de5270e8e45744a7025c24df1f454a4cf0)

3059. By Michel Dänzer <email address hidden> on 2018-12-28

Use drmIoctl in drmmode_show_cursor

This should be functionally equivalent to what drmModeSetCursor(2) do
behind the scenes, but allows for new tricks in following changes.

(Ported from amdgpu commit b344e1559e936046ef02c777fc4f6bcefa3830bc)

3058. By Michel Dänzer <email address hidden> on 2018-12-28

Drop RADEONInfoRec::cursor_bo array

Not needed or even useful for anything.

(Ported from amdgpu commit e95044e45350870fa7e237860e89ade91ac03550)

3057. By Michel Dänzer <email address hidden> on 2018-12-28

Automatically try re-enabling TearFree after a flip failed

Specifically, after both the page flip and vblank ioctls failed, but
then the vblank ioctl started working again. This can happen
intermittently e.g. when hotplugging a DP display. Previously, TearFree
would stay disabled in that case until a modeset was triggered somehow.

Bugzilla: https://bugs.freedesktop.org/103791
(Ported from amdgpu commit bcfa6c258fdf41a9928f8a3c78fc528d0fafee25)

3056. By Michel Dänzer <email address hidden> on 2018-12-28

Cancel pending scanout update in drmmode_crtc_scanout_update

drmmode_crtc_scanout_update does the equivalent of a scanout update,
so no need to do it again. This might also avoid issues if there's a
pending scanout update at this point.

(Ported from amdgpu commit 4e7a24ac5a64e402146953ec5850d13c05742116)

3055. By Michel Dänzer <email address hidden> on 2018-12-28

Perform scanout buffer update immediately if drmmode_wait_vblank fails

Otherwise the damaged screen contents may never be displayed in that
case.

(Ported from amdgpu commit 500fadb16285146e91f62fce3a0ce1360ca684ba)

3054. By Michel Dänzer <email address hidden> on 2018-12-28

Move deferred vblank events to separate drm_vblank_deferred list

It was still possible for nested xorg_list_for_each_entry_safe loops
to occur over the drm_vblank_signalled list, which could mess up that
list. Moving deferred events to a separate list allows processing the
drm_vblank_signalled list without xorg_list_for_each_entry_safe.

Bugzilla: https://bugs.freedesktop.org/108600
(Ported from amdgpu commit 51ba6dddee40c3688d4c7b12eabeab516ed153b7)

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers

No subscribers.