[PATCH v6 03/11] randr: Add ability to turn PRIME sync off

Adds an output parameter to disable PRIME synchronization. Output parameter is created when the user calls 'xrandr --setprovideroutputsource ' to prevent polluting output parameters of non-PRIME configurations. Defaults to on, so if the user wants PRIME synchronization they don't need to do

[PATCH v6 11/11] modesetting: Implement PRIME syncing as a source

Implements (Start/Stop)FlippingPixmapTracking, PresentSharedPixmap, and RequestSharedPixmapNotifyDamage, the source functions for PRIME synchronization and double buffering. Allows modesetting driver to be used as a source with PRIME synchronization. v1: N/A v2: N/A v3: N/A v4: Initial commit v5:

[PATCH v6 09/11] modesetting: Blacklist UDL from PRIME sync

UDL (USB 2.0 DisplayLink DRM driver) has strange semantics when it comes to vblank events and damage tracking when page flipping. When doing a page flip, it will instantly raise a vblank event without waiting for vblank. However, it has no support for DRM_IOCTL_WAIT_VBLANK. It also seems to have

[PATCH v6 07/11] modesetting: Implement PRIME syncing as a sink

Implements (Enable/Disable)SharedPixmapFlipping and SharedPixmapNotifyDamage, the sink functions for PRIME synchronization and double buffering. Allows modesetting driver to be used as a sink with PRIME synchronization. Changes dispatch_slave_dirty to flush damage from both scanout pixmaps.

[PATCH v6 10/11] modesetting: Disable Reverse PRIME for i915

Reverse PRIME seems to be designed with discrete graphics as a sink in mind, designed to do an extra copy from sysmem to vidmem to prevent a discrete chip from needing to scan out from sysmem. The criteria it used to detect this case is if we are a GPU screen and Glamor accelerated. It's possible

[PATCH v6 05/11] modesetting: Always tear down scanout pixmap

drmmode_set_scanout_pixmap_(cpu/gpu) would only do teardown if ppix == NULL. This meant that if there were consecutive calls to SetScanoutPixmap(ppix != NULL) without calls to SetScanoutPixmap(ppix == NULL) in between, earlier calls would be leaked. RRReplaceScanoutPixmap() does this today.

[PATCH v6 00/11] PRIME Synchronization

Hello all, This patch set is identical to v5, except that it's rebased onto ToT, including Dave's alternative implementation of one of my patches, commit a6b6e8ba. In the last thread, Dave said that "with this rebased onto that, we should be pretty much good to merge," so that is my hope. These

[PATCH v6 02/11] randr/xf86: Add PRIME Synchronization / Double Buffer

Changes PRIME to use double buffering and synchronization if all required driver functions are available. rrcrtc.c: Changes rrSetupPixmapSharing() to use double buffering and synchronization in the case that all required driver functions are available. Otherwise, falls back to

[PATCH v6 01/11] xf86: Add PRIME flipping functions to Screen

Adds typedefs for (*RRStartFlippingPixmapTrackingProcPtr), (*RREnableSharedPixmapFlippingProcPtr), and (*RRDisableSharedPixmapFlippingProcPtr) in randrstr.h. Adds typedefs for (*PresentSharedPixmapProcPtr), (*SharedPixmapNotifyDamageProcPtr), (*RequestSharedPixmapNotifyDamageProcPtr), and

[PATCH v6 08/11] modesetting: Suspend and resume flipping with DPMS

DPMS would prevent page flip / vblank events from being raised, freezing the screen until PRIME flipping was reinitialized. To handle DPMS cleanly, suspend PRIME page flipping when DPMS mode is not on, and resume it when DPMS mode is on. v1: Initial commit v2: Moved flipping_active check from

[PATCH v6 06/11] modesetting: Always load ms->drmmode.pageflip

ms->drmmode.pageflip was only loaded from options if ms->drmmode.glamor was defined, otherwise it would always assume FALSE. PRIME Synchronization requires ms->drmmode.pageflip even if we aren't using glamor, so load it unconditionally. v1: N/A v2: N/A v3: N/A v4: N/A v5: Initial commit v6:

[PATCH v6 04/11] modesetting: Internal storage of scanout pixmaps

modesetting relied on randr_crtc->scanout_pixmap being consistent with calls to SetScanoutPixmap, which is very fragile and makes a lot of assumptions about the caller's behavior. For example, RRReplaceScanoutPixmap(), when dropping off with !size_fits, will set randr_crtc->scanout_pixmap = NULL

Re: [PATCH xserver 2/4] xace: Remove the audit hooks and tune dispatch

Adam Jackson writes: > On Fri, 2016-04-29 at 14:22 -0400, Adam Jackson wrote: >> There are no in-tree consumers of the audit hooks, and they are in any >> case redundant with the dtrace dispatch hooks. Neither is there any >> in-tree user of the core request dispatch hook. The

Re: switching the server to poll/epoll

Adam Jackson writes: > Protip: git rebase -i -x make master Thanks. Will do. I spent a bunch of time re-ordering stuff to make it more understandable, and not enough time testing the individual patches. -- -keith signature.asc Description: PGP signature

Re: [PATCH xserver 0/3] Accounting fixes for ResQueryClientPixmapBytes

On Tue, 2016-02-02 at 14:30 -0500, Adam Jackson wrote: > In (attempting to) track down a memory leak, I found that the pixmap byte > accounting code in the Resource extension was wildly overreporting.  This > series tries to fix things up, and even deletes some code in the process. > Sadly it does

Re: [PATCH xserver 2/4] xace: Remove the audit hooks and tune dispatch

On Fri, 2016-04-29 at 14:22 -0400, Adam Jackson wrote: > There are no in-tree consumers of the audit hooks, and they are in any > case redundant with the dtrace dispatch hooks. Neither is there any > in-tree user of the core request dispatch hook. The extension hook is > only used for non-default

Re: switching the server to poll/epoll

On Wed, 2016-06-01 at 23:40 -0700, Keith Packard wrote: > > And yet more changes to my poll/epoll work. Peter and I discovered that > the threaded input code wasn't doing locking correctly, which was easy > enough to fix on master, but required a bit more work with the new > ospoll interface.

[PATCH kdrive/ephyr] ephyr: use XCB_EVENT_RESPONSE_TYPE macro

Signed-off-by: Laércio de Sousa --- hw/kdrive/ephyr/ephyr.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hw/kdrive/ephyr/ephyr.c b/hw/kdrive/ephyr/ephyr.c index fe947db..5a8d9ef 100644 --- a/hw/kdrive/ephyr/ephyr.c +++

[PATCH vmmouse] conf: rename to 70-vmmouse.conf

Bump up the vmmouse driver to 70, so it get's preferred over libinput, which was dropped down to 60. This is only relevant for older kernels, which do not yet have the functionality provided by vmmouse driver. On recent kernels vmmouse driver is no longer loaded at all. Signed-off-by: Stefan