similar to: [PATCH] drmmode: update logic for dynamic connectors, paths, and tiles

This largely copies the code from modesetting with minor adjustments. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I've tested this back and forth with a GTX 960 + 2x U2415 monitors, chained to each other. I turned them on/off. I messed with their DP 1.1/1.2 settings. I pulled plugs a few times. This seems to pass the test. No crashes, the connectors seem to come and go

Straight port of Matthias Hopf's KMS backlight code for xf86-video-intel, with reformatting and a couple of minor cleanups. Works fine on my MacBookAir2,1. Signed-off-by: Daniel Stone <daniel at fooishbar.org> --- src/drmmode_display.c | 269 ++++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 268 insertions(+), 1 deletions(-) diff --git a/src/drmmode_display.c

I don't understand this patch (what are all these masks? how are they used?), and don't want to invest the time required to do so. However Mario is probably the sole serious user of ZaphodHeads, and if it fixes issues for him, probably fixes issues for others who try and give up with ZaphodHeads. Any objections if I just push this out? On Sat, Jun 27, 2015 at 8:33 PM, Mario Kleiner

In multi-x-screen ZaphodHeads configurations, there isn't a one-to-one mapping of kernel provided drmmode crtc index to the index of the corresponding xf86Crtc inside the xf86CrtcConfig crtc array anymore, ie. for kernel provided drmmode->mode_res->crtcs[i], the i'th crtc won't correspond to the xf86Crtc in the i'th slot of the x-screens xf86CrtcConfig anymore, once

This reverts commit 98c9e4edb58374f18249e5c9c53b392fb8b4a1d1. AFAIK it's no longer needed. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/drmmode_display.c | 3 --- src/nv_driver.c | 2 -- src/nv_type.h | 1 - 3 files changed, 0 insertions(+), 6 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 7c45d9c..a91741d

From: Dave Airlie <airlied at redhat.com> This adds support to detect libbacklight and use it to provide the standard randr backlight properties, for desktops environments to use. untested as of yet. Signed-off-by: Dave Airlie <airlied at redhat.com> --- configure.ac | 3 +++ src/Makefile.am | 4 ++-- src/drmmode_display.c | 40

[PATCH 1/3] kms: Don't hardcode the output properties [PATCH 2/3] kms: Implement output->get_property when RandR1.3 is available. [PATCH 3/3] kms: Add TV-out support src/drmmode_display.c | 403 ++++++++++++++++++++++++++++++++----------------- 1 files changed, 261 insertions(+), 142 deletions(-)

This is probably a typo error which has been introduced in 2009... This fixes the following warning detected by Clang : drmmode_display.c:907:30: warning: use of logical '&&' with constant operand [-Wconstant-logical-operand] if (props && (props->flags && DRM_MODE_PROP_ENUM)) { Signed-off-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> ---

This is obviously a bug, but one that has been there for some time. Please figure out what this is guarding, and confirm that the feature continues to work. On Wed, May 20, 2015 at 1:11 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > looks good to me! :) > > Feel free to add my R-b. > > On 20.05.2015 17:08, Samuel Pitoiset wrote: >> >> This

Keeping it in VRAM wastes CPU time, because cursor_set ioctl reads handed BO back to RAM, just to write it to actual cursor BO. Here (nv92/core i7), this patch decreases overall cpu usage of drmmode_load_cursor_argb from 4.6ms to ~90us and lets nv50_crtc_cursor_set disappear from perf traces. --- I considered accelerating kernel-side copying with GPU, but it turns out that: - it's slower

From: Dave Airlie <airlied at redhat.com> This is preperation for the backlight support code. Signed-off-by: Dave Airlie <airlied at redhat.com> --- src/drmmode_display.c | 54 ++++++++++++++++++++++++++++++++------------------- 1 file changed, 34 insertions(+), 20 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 6033a6d..ad7bc1f 100644 ---

Hi Ilia, Ben, et al. Can I please get a review of this patch, and assuming the review is favorable, can someone please push this ? Regards, Hans p.s. Is it ok if I request push rights to the nouveau repos / group at freedesktop.org ? On 03-06-16 14:46, Hans De Goede wrote: > drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call > to drmmode_xf86crtc_resize(), but on a

drmmode_set_scanout_pixmap(pix) adds drmmod->fb_id through a call to drmmode_xf86crtc_resize(), but on a subsequent drmmode_set_scanout_pixmap(NULL) it would not remove the fb. This keeps the crtc marked as busy, which causes the dgpu to not being able to runtime suspend, after an output attached to the dgpu has been used once. Which causes burning through an additional 10W of power and the

I'm pleased to announce the 1.1.0 release of xf86-video-amdgpu, the Xorg driver for AMD Radeon GPUs supported by the amdgpu kernel driver. This release supports xserver versions 1.9-1.18. Highlights: * Support for the upcoming Polaris family of GPUs. * Option "TearFree" can now prevent tearing with rotation/reflection as well (with Xorg >= 1.16). * RandR CRTC transforms now

https://bugs.freedesktop.org/show_bug.cgi?id=106994 Bug ID: 106994 Summary: [PATCH] Fix null pointer dereference in drmmode_output_dpms Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

Apparently it now wants a drawable. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- No idea about whether this is correct. Saw the new warnings though. src/drmmode_display.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 2480122..f677e24 100644 --- a/src/drmmode_display.c +++

From: Michel Dänzer <michel.daenzer at amd.com> This allows making the master screen's pixmap_dirty_list entries explicitly reflect that we're now tracking the root window instead of the screen pixmap, in order to allow Present page flipping on master outputs while there are active slave outputs. Define HAS_DIRTYTRACKING_DRAWABLE_SRC for drivers to check, but leave

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Khem Raj (1): drmmode_output_dpms: Replace logical && with bitwise & operation Rob Clark (1): NEWS: Bump version to 0.4.4 Robert Nelson (1): add support for AM572x in the DDX Steve Wilkins (2): drmmode: Fix crash with multi-crtc page-flip drmmode: Fix leaked fb in case of failed pageflip

Hi! I've written a small amount of code that gets the randr 1.2 branch much closer to working for me on a laptop. Most of the changes are fairly obvious, but a couple of comments: 1) The changes to nv_crtc.c are clearly bogus, but I'm not sure what on earth these registers do. I need to set them to get a moderately sane-looking picture 2) The fp registers poked in nv_output.c

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Full log below, but most notably: - Better 30bpp handling - DP-MST hotplug support - DRI3/Present support in the presence of rotated RandR screens - Updates for various Xorg API changes - Autoconf cleanups Adam Jackson (1): modesetting: Validate the atom for enum properties Ilia Mirkin (10): man: remove reference to glamor under