[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

xorg-server: Changes to 'ubuntu'



 debian/changelog                                 |    7 ++
 debian/patches/series                            |    2 
 debian/patches/xf86-dont-enable-gpuscreens.patch |   64 +++++++++++++++++++++++
 3 files changed, 72 insertions(+), 1 deletion(-)

New commits:
commit 73f1016acdd805e2a71af6f3add911355d0842a6
Author: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Date:   Wed May 1 09:41:48 2013 +0200

    Add patch to fixup optimus again, and release to saucy.

diff --git a/debian/changelog b/debian/changelog
index 97c7ad9..0dd047d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xorg-server (2:1.13.3-0ubuntu7) saucy; urgency=low
+
+  * Add patch to fixup optimus again.
+    - xf86-dont-enable-gpuscreens.patch
+
+ -- Maarten Lankhorst <maarten.lankhorst@ubuntu.com>  Wed, 01 May 2013 10:35:55 +0200
+
 xorg-server (2:1.13.3-0ubuntu6) raring; urgency=low
 
   * SECURITY UPDATE: input event leak via inactive VT
diff --git a/debian/patches/series b/debian/patches/series
index b207b1c..9af5361 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -34,9 +34,9 @@ xephyr-glx-register.patch
 no-nv.patch
 
 ## waiting for review by upstream
+xf86-dont-enable-gpuscreens.patch
 111_armel-drv-fallbacks.patch
 500_pointer_barrier_thresholds.diff
-
 ## upstream patches
 os-use-libunwind-to-generate-backtraces.patch
 
diff --git a/debian/patches/xf86-dont-enable-gpuscreens.patch b/debian/patches/xf86-dont-enable-gpuscreens.patch
new file mode 100644
index 0000000..64531ab
--- /dev/null
+++ b/debian/patches/xf86-dont-enable-gpuscreens.patch
@@ -0,0 +1,64 @@
+From: Aaron Plattner <aplattner@nvidia.com>
+To: <xorg-devel@lists.x.org>
+Subject: [PATCH] xfree86: don't enable anything in xf86InitialConfiguration
+	for GPU screens
+Date: Tue, 30 Apr 2013 14:30:18 -0700
+
+There's no point in turning on outputs connected to GPU screens during initial
+configuration.  Not only does this cause them to just display black, it also
+confuses clients when these screens are attached to a master screen and RandR
+reports that the outputs are already on.
+
+Also, don't print the warning about no outputs being found on GPU screens,
+since that's expected.
+
+Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
+---
+Dave, this fixes the black screen problem with "gpu: call CreateScreenResources
+for GPU screens"
+
+ hw/xfree86/modes/xf86Crtc.c | 16 +++++++++++++---
+ 1 file changed, 13 insertions(+), 3 deletions(-)
+
+diff --git a/hw/xfree86/modes/xf86Crtc.c b/hw/xfree86/modes/xf86Crtc.c
+index 4a490c6..35845e8 100644
+--- a/hw/xfree86/modes/xf86Crtc.c
++++ b/hw/xfree86/modes/xf86Crtc.c
+@@ -1997,6 +1997,14 @@ xf86CollectEnabledOutputs(ScrnInfoPtr scrn, xf86CrtcConfigPtr config,
+     Bool any_enabled = FALSE;
+     int o;
+ 
++    /*
++     * Don't bother enabling outputs on GPU screens: a client needs to attach
++     * it to a source provider before setting a mode that scans out a shared
++     * pixmap.
++     */
++    if (scrn->is_gpu)
++        return FALSE;
++
+     for (o = 0; o < config->num_output; o++)
+         any_enabled |= enabled[o] = xf86OutputEnabled(config->output[o], TRUE);
+ 
+@@ -2466,9 +2474,11 @@ xf86InitialConfiguration(ScrnInfoPtr scrn, Bool canGrow)
+ 
+     ret = xf86CollectEnabledOutputs(scrn, config, enabled);
+     if (ret == FALSE && canGrow) {
+-        xf86DrvMsg(i, X_WARNING,
+-                   "Unable to find connected outputs - setting %dx%d initial framebuffer\n",
+-                   NO_OUTPUT_DEFAULT_WIDTH, NO_OUTPUT_DEFAULT_HEIGHT);
++        if (!scrn->is_gpu)
++            xf86DrvMsg(i, X_WARNING,
++		       "Unable to find connected outputs - setting %dx%d "
++                       "initial framebuffer\n",
++                       NO_OUTPUT_DEFAULT_WIDTH, NO_OUTPUT_DEFAULT_HEIGHT);
+         have_outputs = FALSE;
+     }
+     else {
+-- 
+1.8.2.2
+
+_______________________________________________
+xorg-devel@lists.x.org: X.Org development
+Archives: http://lists.x.org/archives/xorg-devel
+Info: http://lists.x.org/mailman/listinfo/xorg-devel
+


Reply to: