On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
On Sun, Dec 9, 2012 at 12:16 PM, olivier.e.am...@gmail.com wrote:
When starting openSuse 12.2, the X-server terminates with a
segmentation fault (see attached log file).
The open source driver should support your card just
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
On Sun, Dec 9, 2012 at 12:16 PM, olivier.e.am...@gmail.com
wrote:
When starting openSuse 12.2, the X-server terminates with a
segmentation fault (see
On Die, 2012-12-11 at 02:48 -0800, stompdagg...@yahoo.com wrote:
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
On Sun, Dec 9, 2012 at 12:16 PM, olivier.e.am...@gmail.com
wrote:
When starting
On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com
stompdagg...@yahoo.com wrote:
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
On Sun, Dec 9, 2012 at 12:16 PM, olivier.e.am...@gmail.com
wrote:
When
On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com
stompdagg...@yahoo.com wrote:
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
On Sun, Dec 9, 2012 at 12:16 PM, olivier.e.am...@gmail.com
wrote:
When
From: Daniel Martin daniel.mar...@secunet.com
Hi,
the following patch removes the resize restriction from Xephyr by adding
a new option -resizeable. With that option it's possible to resize
Xephyr windows without the need of an explicit parent window.
Cheers,
Daniel Martin (1):
ephyr: Add
From: Daniel Martin daniel.mar...@secunet.com
With this option passed, ephyr windows can be resized like normal
windows on the fly, without the need of an explicit parent window.
Signed-off-by: Daniel Martin daniel.mar...@secunet.com
---
hw/kdrive/ephyr/ephyr.c |1 +
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
hw/xfree86/common/xf86Events.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/xfree86/common/xf86Events.c b/hw/xfree86/common/xf86Events.c
index 9dabf10..d8d4fad 100644
--- a/hw/xfree86/common/xf86Events.c
+++
So this got merged into Fedora, and nobody reads bug reports after
merging stuff to know when it breaks lots of things.
}
+/*
+ * If all of the above fails, which can happen if X was started without
+ * configuration or if BusID wasn't set for non-PCI devices, use the
first
On Wed, Dec 12, 2012 at 11:49 AM, Dave Airlie airl...@gmail.com wrote:
So this got merged into Fedora, and nobody reads bug reports after
merging stuff to know when it breaks lots of things.
}
+/*
+ * If all of the above fails, which can happen if X was started without
+ *
Hi Keith,
the dri1 fix has gone unreviewed on the list, even by those who
created the problem, but it works here and I'd rather not forget it
again.
The non-pci change breaks all multi-gpu setups in Fedora here, so we
should drop it for now until we know what is the correct way to
implement it,
From: Dave Airlie airl...@redhat.com
Due to another bug, the modesetting/udl driver would fail to init properly
on hotplug, when it did the code didn't clean up properly, and on removing
the device the server could crash.
Found in F18 testing.
Signed-off-by: Dave Airlie airl...@redhat.com
---
This is the server-side for the pointer-barrier patches, proposed as XI 2.3.
It adds events for pointer barriers (when the pointer hits vs leaves the
arrier) and the ability to release a pointer across. I hereby propose this
for the 1.14 release.
Trees for testing available from:
From: Jasper St. Pierre jstpie...@mecheye.net
In order to send events to specific windows associated with the barrier,
we need to move the code that handles barriers to somewhere where it's
easier to construct and send events. Rather than duplicating XSync with
its XSyncSelectAlarm, re-use the
From: Jasper St. Pierre jstpie...@mecheye.net
This is completely pointless as far as I can tell.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 16 ++--
1 file changed, 2 insertions(+), 14 deletions(-)
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
From: Jasper St. Pierre jstpie...@mecheye.net
Rather than riding on the ConstrainCursorHarder hook, which has
several issues, move to an explicit hook, which will help us with
some RANDR interaction issues.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 56
From: Jasper St. Pierre jstpie...@mecheye.net
When we add events, we eventually want to add more state to the
PointerBarrierClient, so return one of these instead of the dummy
public structure that's not very interesting.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
From: Jasper St. Pierre jstpie...@mecheye.net
This is to make future diffs much cleaner. Best viewed with -w.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 57 +
1 file changed, 29 insertions(+), 28
From: Jasper St. Pierre jstpie...@mecheye.net
This adds support for clients that would like to get a notification
every time a barrier is hit, and allows clients to temporarily release
a barrier so that pointers can go through them, without having to
destroy and recreate barriers.
Based on work
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
index f16094d..86e811e 100644
--- a/Xi/xibarriers.c
+++ b/Xi/xibarriers.c
@@ -534,6 +534,9 @@ XIDestroyPointerBarrier(ClientPtr
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
index 86e811e..8f12253 100644
--- a/Xi/xibarriers.c
+++ b/Xi/xibarriers.c
@@ -591,6 +591,9 @@ ProcXIBarrierReleasePointer(ClientPtr
From: Jasper St. Pierre jstpie...@mecheye.net
If we release a barrier, we want to ensure that we block all
other barriers afterwards, rather than capping the limit to
the two nearest barriers.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 7 ---
1 file
From: Jasper St. Pierre jstpie...@mecheye.net
Pointers (and the hands that drive them) aren't very precise, and the
slightest amount of nudging to either side might be enough to reset
the event ID, making clients think they have an entirely new hit. Allow
for a slightly bigger hit box before
From: Jasper St. Pierre jstpie...@mecheye.net
We eventually want to send a new notify event on hitbox leave,
which signifies the dawn of a new barrier event ID, so it's
convenient if we can put the code here.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 14
From: Jasper St. Pierre jstpie...@mecheye.net
Additionally, add flags when the pointer is released.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
index
From: Jasper St. Pierre jstpie...@mecheye.net
Rename a variable. This is to make the diff in the next commit cleaner.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Xi/xibarriers.c
From: Jasper St. Pierre jstpie...@mecheye.net
This ensures that we always complete an event sequence.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Xi/xibarriers.c | 44
1 file changed, 44 insertions(+)
diff --git a/Xi/xibarriers.c
From: Jasper St. Pierre jstpie...@mecheye.net
Since barriers are axis-aligned, we can do the intersection test with
simple interpolation rather than line-segment intersection. This also
helps us out in the future when we want the barriers to extend to be
rays and lines rather than just segments.
From: Jasper St. Pierre jstpie...@mecheye.net
This allows clients to add barriers that extend to the edge of the
screen. Clients are encouraged to use these instead of precise coordinates
in these cases to help prevent pointer leaks.
Signed-off-by: Jasper St. Pierre jstpie...@mecheye.net
---
Instead of having the pointer barrier code enqueue events separately from
GetPointerEvents, pass the event list through and let it add to it.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 15 ---
dix/getevents.c | 15 +++
include/input.h |
x/y for barrier events should contain the actual pointer position.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/xibarriers.c | 4
mi/mipointer.c | 18 +-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
index
Only deliver to the client that created the barrier, not to other clients.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
dix/events.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/dix/events.c b/dix/events.c
index 3282ef8..49b8bc5 100644
---
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
dix/eventconvert.c | 4
1 file changed, 4 insertions(+)
diff --git a/dix/eventconvert.c b/dix/eventconvert.c
index bb5c8d3..47dcf8b 100644
--- a/dix/eventconvert.c
+++ b/dix/eventconvert.c
@@ -161,6 +161,8 @@
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
dix/events.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dix/events.c b/dix/events.c
index 49b8bc5..c98a2de 100644
--- a/dix/events.c
+++ b/dix/events.c
@@ -2436,6 +2436,8 @@ FixUpEventFromWindow(SpritePtr pSprite,
case
If the grab_window is the barrier window and the client owns the grab,
deliver as normal grabbed event (respecting owner_events). Otherwise,
deliver as usual.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/exevents.c | 18 +++---
1 file changed, 15 insertions(+), 3
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/exevents.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Xi/exevents.c b/Xi/exevents.c
index a7ec0c4..f025dd1 100644
--- a/Xi/exevents.c
+++ b/Xi/exevents.c
@@ -1655,6 +1655,9 @@ ProcessBarrierEvent(InternalEvent *e,
Avoid name shadowing warnings, change the event list to a more specific
name.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
mi/mipointer.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/mi/mipointer.c b/mi/mipointer.c
index 7bc0983..b8503f4
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 38ac240..ee0fa78 100644
--- a/configure.ac
+++ b/configure.ac
@@ -788,7 +788,7 @@ XPROTO=xproto = 7.0.22
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/xi2/protocol-eventconvert.c | 216 +++
1 file changed, 216 insertions(+)
diff --git a/test/xi2/protocol-eventconvert.c b/test/xi2/protocol-eventconvert.c
index bb3177c..3957747 100644
---
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/extinit.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Xi/extinit.c b/Xi/extinit.c
index 175d89b..606d61c 100644
--- a/Xi/extinit.c
+++ b/Xi/extinit.c
@@ -847,7 +847,9 @@ SBarrierEvent(xXIBarrierEvent * from,
Protocol events don't contain pointers, so it's easier to copy everything
over, then swap in-place.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Xi/extinit.c | 45 +
1 file changed, 21 insertions(+), 24 deletions(-)
diff --git
GrabMask is a union of core, XI1 and XI2 masks. If a XI2 grab is activated,
the value is a random pointer value, using it as mask has unpredictable
effects.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
dix/grabs.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
Fixes inconsistent touch event selection, a stack smash on some touch
devices and re-fixes 28808 after that came back recently.
The following changes since commit b51a1bd2766e7dc975ca8f1cacc3f8bd0e1a68a3:
Merge remote-tracking branch 'whot/for-keith' (2012-11-30 09:31:46 -0800)
are available
https://bugs.freedesktop.org/show_bug.cgi?id=58119
Priority: medium
Bug ID: 58119
Assignee: xorg-driver-ati@lists.x.org
Summary: EQ overflow when running glxgears in fullscreen mode
QA Contact: xorg-t...@lists.x.org
Severity: normal
On Mon, 2012-12-10 at 13:12 -0600, Ilija Hadzic wrote:
Clearly, the behavior that we have now is wrong from the power-savings
perspective (i.e., it completely defeats the purpose of DPMS),
Not sure I agree with this statement, given DPMS stands for *Display*
Power Management Signaling, but
https://bugs.freedesktop.org/show_bug.cgi?id=58119
--- Comment #1 from Michel Dänzer mic...@daenzer.net ---
Please attach files here directly rather than referencing external sites
whenever possible.
Please also attach the dmesg output, preferably captured after the problem
occurred.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=58119
--- Comment #2 from Vladimir Mityukov mityu...@gmail.com ---
Created attachment 71318
-- https://bugs.freedesktop.org/attachment.cgi?id=71318action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58119
--- Comment #3 from Vladimir Mityukov mityu...@gmail.com ---
Created attachment 71320
-- https://bugs.freedesktop.org/attachment.cgi?id=71320action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58119
--- Comment #4 from Vladimir Mityukov mityu...@gmail.com ---
Created attachment 71321
-- https://bugs.freedesktop.org/attachment.cgi?id=71321action=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58119
Vladimir Mityukov mityu...@gmail.com changed:
What|Removed |Added
Attachment #71318|Xorg.0.log |dmesg
reassign 695594 libgl1-mesa-dri
kthxbye
On Mon, 2012-12-10 at 10:06 -0500, The Wanderer wrote:
I was able to obtain a backtrace according to the instructions on the
XStrikeForce/XServerDebugging page of wiki.debian.org; that is attached.
It crashes in Mesa code, reassigning there.
Note
From: Michel Dänzer michel.daen...@amd.com
../../src/radeon_probe.c: In function 'radeon_platform_probe':
../../src/radeon_probe.c:270:11: error: unused variable 'path'
[-Werror=unused-variable]
Signed-off-by: Michel Dänzer michel.daen...@amd.com
---
src/radeon_probe.c |1 -
1 file
From: Michel Dänzer michel.daen...@amd.com
Signed-off-by: Michel Dänzer michel.daen...@amd.com
---
src/drmmode_display.c |2 --
src/evergreen_textured_videofuncs.c | 12
src/r600_textured_videofuncs.c | 12
src/radeon_textured_videofuncs.c
From: Michel Dänzer michel.daen...@amd.com
Pointed out by clang:
../../src/radeon_kms.c:1562:6: warning: variable 'total_size_bytes' is
uninitialized when used here [-Wuninitialized]
total_size_bytes += (64 * 4 * 64);
^~~~
../../src/radeon_kms.c:1557:25:
From: Michel Dänzer michel.daen...@amd.com
Not actually used for anything. Refactoring gone wrong?
Also remove a comment that doesn't seem to make sense anymore.
Stumbled over this due to a warning by clang:
../../src/radeon_kms.c:1562:6: warning: variable 'total_size_bytes' is
uninitialized
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #13 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #13)
Before this didn't happen, it's a new bug.
It didn't happen before what? It would be great if you could isolate which
component (kernel, xf86-video-ati, mesa)
https://bugs.freedesktop.org/show_bug.cgi?id=57995
--- Comment #4 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #4)
1. I'm always in X
2. I have a window that extends or is moved offscreen to the left.
3. I move the mouse offscreen to the left.
Hmm, if it only happens when
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #6 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #6)
attempt to enable the all three panels (This should not be allowed to work
but it passes even though it should fail )
Why should it fail?
restart pc
attempt
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #14 from Rubén Reina ruben.reina@gmail.com ---
I was using an older version of the driver, this problem appeared when I
installed version 1:7.0.0+git1212071424.793e1b (xserver-xorg-video-ati).
I was working with mesa 9.1 without
On Tue, Dec 11, 2012 at 6:10 AM, Michel Dänzer mic...@daenzer.net wrote:
From: Michel Dänzer michel.daen...@amd.com
Signed-off-by: Michel Dänzer michel.daen...@amd.com
For the series and your v2 patch:
Reviewed-by: Alex Deucher aleander.deuc...@amd.com
---
src/drmmode_display.c
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #15 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #14)
I was using an older version of the driver, this problem appeared when I
installed version 1:7.0.0+git1212071424.793e1b (xserver-xorg-video-ati).
What was the
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #7 from Kenney Phillis Jr kphilli...@gmail.com ---
(In reply to comment #6)
(In reply to comment #6)
attempt to enable the all three panels (This should not be allowed to work
but it passes even though it should fail )
Why
https://bugs.freedesktop.org/show_bug.cgi?id=57995
--- Comment #5 from David Ronis david.ro...@mcgill.ca ---
I'll turn composting on when I get home. I the mean time, someone wrote me
(strange that it didn't appear here as well), who was having similar problems
and suggested that I turn AccelDFS
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #8 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #7)
The hardware doesn't support it... Even when I enabled the third display and
used all three at once only two displays had output... In my case the
following
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #16 from Rubén Reina ruben.reina@gmail.com ---
The older version was the version that comes installed with Ubuntu 12.04 by
default (don't know how to see it). I can't disable ColorTiling2D because I
don't have xorg.conf file in my
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #17 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #16)
The older version was the version that comes installed with Ubuntu 12.04 by
default (don't know how to see it). I can't disable ColorTiling2D because I
don't have
https://bugs.freedesktop.org/show_bug.cgi?id=57990
--- Comment #18 from Rubén Reina ruben.reina@gmail.com ---
Thank you very much, I'll create that xorg.conf and I'll tell you if that
works. I'm outside home now but in two days I'll do it.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #9 from Kenney Phillis Jr kphilli...@gmail.com ---
Created attachment 71359
-- https://bugs.freedesktop.org/attachment.cgi?id=71359action=edit
Xrandr verbose output ( radeon driver )
Xorg version:
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #10 from Alex Deucher ag...@yahoo.com ---
Can you list the exact commands you are using? I can't reproduce this here. I
have a APU laptop with VGA-0, HDMI-0, and LVDS and I get the expected behavior:
$ xrandr --output HDMI-0 --auto
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #11 from Alex Deucher ag...@yahoo.com ---
Do you still have the GPU resets when you disable acceleration?
Option NoAccel true
in the device section of your xorg.conf
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=58115
Kenney Phillis Jr kphilli...@gmail.com changed:
What|Removed |Added
Summary|AMD LLANO repeated gpu |AMD LLANO
https://bugs.freedesktop.org/show_bug.cgi?id=58115
--- Comment #12 from Kenney Phillis Jr kphilli...@gmail.com ---
Created attachment 71371
-- https://bugs.freedesktop.org/attachment.cgi?id=71371action=edit
xrandr tests -- radeon driver
it appears the problem is user space... xrandr command
72 matches
Mail list logo
