-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Langdale (5):
Narrow down the scope of what systems are checked for the vmmouse device.
Don't flush buttons.
Only turn on absolute mode when we get an actual event; we don't
Revert Narrow down the scope of what systems
From: Peter Hutterer [EMAIL PROTECTED]
Preparation for the new core enter/leave model.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/Makefile.am |2 +
dix/enterleave.c | 138 ++
dix/enterleave.h | 53 +
From: Peter Hutterer [EMAIL PROTECTED]
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/events.c| 15 ---
include/input.h |1 -
2 files changed, 0 insertions(+), 16 deletions(-)
diff --git a/dix/events.c b/dix/events.c
index 1ac45e3..eff7eeb 100644
---
From: Peter Hutterer [EMAIL PROTECTED]
Device events always need to be delivered, core events only in some cases.
Let's keep them completely separate so we can adjust core event delivery.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/enterleave.c | 76 +++---
From: Peter Hutterer [EMAIL PROTECTED]
FirstPointerChild: Return the first child that has a pointer within its
boundaries.
FirstPointerAncestor: return the first ancestor with a child within its
boundaries.
These are required for the updated enter/leave model.
Signed-off-by: Peter Hutterer
From: Peter Hutterer [EMAIL PROTECTED]
---
include/input.h |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/include/input.h b/include/input.h
index 5377d23..c78f0b7 100644
--- a/include/input.h
+++ b/include/input.h
@@ -97,12 +97,6 @@ SOFTWARE.
#define
From: Peter Hutterer [EMAIL PROTECTED]
These replace the ENTER_LEAVE_SEMAPHORE_* macros. Unused currently.
Signed-off-by: Peter Hutterer [EMAIL PROTECTED]
---
dix/enterleave.c | 38 ++
1 files changed, 38 insertions(+), 0 deletions(-)
diff --git
As simple as it gets.
Fernando Carrijo.
---
dix/events.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/dix/events.c b/dix/events.c
index 7ec5355..c47c52a 100644
--- a/dix/events.c
+++ b/dix/events.c
@@ -5227,8 +5227,6 @@ ProcUngrabKeyboard(ClientPtr client)
On Thu, 2008-11-13 at 13:03 -0500, Alex Villacís Lasso wrote:
Michel Dänzer escribió:
On Mon, 2008-11-10 at 13:37 -0500, Alex Villacís Lasso wrote:
The question is: is there any xserver support that might enable a driver
to get pixmap data into either kind of situation? Either get
I'm using Xorg 1.4.2, and when I unplug my Logitech mouse from my
laptop, X restarts and brings me back to the xdm login screen.
I tried both the evdev and the mouse driver, with the same result (chose
to stay with mouse for now as I couldn't get evdev to work with my
keyboard and configure the
xcompmgr is a good example too. It's quite straightforward once you rip
out the code to handle/generate shadows.
Thank you.
OK, but I find examples for better understaning principles of usage this
extension (and also XFixes, XDamage, etc.).
So, I prefer more illustration around code.
--
Hi Cliff,
I saw your posting here:
http://lists.freedesktop.org/archives/xorg/2008-September/038581.html
and wondered if you or anyone else managed to resolve this.
I'm cross compiling xorg-server-1.4 for a powerpc 7400 (MAC G4) and
Xfbdev starts and the mouse works (eventually), but I get
Hi Stuart,
I have no idea about your problem, but for what it's worth have you
considered just using Xorg instead of kdrive?
John
2008/11/14 Stuart Hughes [EMAIL PROTECTED]:
Hi Cliff,
I saw your posting here:
http://lists.freedesktop.org/archives/xorg/2008-September/038581.html
and
On Thu, Nov 13, 2008 at 11:40 PM, Matija Šuklje [EMAIL PROTECTED] wrote:
Dne petek 14. novembra 2008 je Peter Hutterer napisal(a):
devices configured in the xorg.conf are not hotplug-capable.
So the proper way would be to migrate the whole InputDevice mouse section to
an .fdi file for HAL to
Hi John,
Thanks for the reply. I don't think I can use Xorg as the box I'm on
only has framebuffer
Anyhow, I just tried 1.4.2 and this works. I still have some warnings
when I start which I'm not sure about, but otherwise all seems okay.
This is what I see:
$ ssh macg4 -l root
~ # Xfbdev -ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Resending with correct subject...
Philip Langdale (5):
Narrow down the scope of what systems are checked for the vmmouse device.
Don't flush buttons.
Only turn on absolute mode when we get an actual event; we don't
Revert
I fixed it in the apple branches, but for some reason it didn't get
into master. It's fixed now:
original:
http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=3ec234976079d30f10e5246f6847a7eee01c144e
master:
You may want update drv-evdev to 2.0.7
On Fri, 2008-11-14 at 14:08 +0100, (none) wrote:
I'm using Xorg 1.4.2, and when I unplug my Logitech mouse from my
laptop, X restarts and brings me back to the xdm login screen.
I tried both the evdev and the mouse driver, with the same result (chose
On Fri, Nov 14, 2008 at 7:24 AM, Stuart Hughes [EMAIL PROTECTED] wrote:
Hi John,
Thanks for the reply. I don't think I can use Xorg as the box I'm on
only has framebuffer
Anyhow, I just tried 1.4.2 and this works. I still have some warnings
when I start which I'm not sure about, but
On 13:13 Fri 14 Nov , Keith Packard wrote:
Here's a proposed schedule of events:
Cut a release branch, do a -RC1 release: 11/24
Track remaining work on scheduled features,
cherry-picking commits from master. Cut -RC2 12/8
Stop accepting new code, focus on bug fixing.
Cut -RC3
These values need not be constrained to integer values.
Signed-off-by: Keith Packard [EMAIL PROTECTED]
---
hw/xfree86/common/xf86Xinput.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/xfree86/common/xf86Xinput.c b/hw/xfree86/common/xf86Xinput.c
index
Hi,
Do you think there is any chance of getting the gradient hooks into 1.6?
Would not be too bad if no driver is able to accalerate it for now,
but at least users would not need xserver 1.7 to get accalerated
gradients.
Distributors usually tend to update drivers, but they almost never
switch to
---
configure.ac |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index 90cacd7..5e1f860 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1191,7 +1191,7 @@ AC_MSG_RESULT([$XNEST])
AM_CONDITIONAL(XNEST, [test x$XNEST = xyes])
if test x$XNEST
---
render/matrix.c | 36 +++-
render/picturestr.h | 11 ---
2 files changed, 43 insertions(+), 4 deletions(-)
diff --git a/render/matrix.c b/render/matrix.c
index bd584cb..a976304 100644
--- a/render/matrix.c
+++ b/render/matrix.c
@@ -222,7 +222,7
To prepare for RandR using filters in transforms, split out
code paths so that the RandR code can validate the filter name and
parameters during the transform set operation so that use of the filter
later will not have unreportable errors.
---
render/filter.c | 57
---
hw/xfree86/modes/xf86Cursors.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/hw/xfree86/modes/xf86Cursors.c b/hw/xfree86/modes/xf86Cursors.c
index a7ed5c4..7bf9265 100644
--- a/hw/xfree86/modes/xf86Cursors.c
+++ b/hw/xfree86/modes/xf86Cursors.c
@@ -37,6
It doesn't make sense to have the client invert this matrix when the server
can do so reasonably efficiently. This avoids weird fixed point rounding
errors when testing the transform against its inverse. Now to fix the
protocol.
---
randr/rrcrtc.c |5 ++---
1 files changed, 2 insertions(+), 3
This eliminates some ugly flashing, as well as clearing the borders when the
shadow will not be completely painted.
---
hw/xfree86/modes/xf86Rotate.c | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/hw/xfree86/modes/xf86Rotate.c
It is easier, and potentially more precise, to compute the inverse in the
server where everything can eventually be kept in floating point form.
---
randr/rrcrtc.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/randr/rrcrtc.c b/randr/rrcrtc.c
index 6559d51..e0fafce
This involved removing a pile of matrix code from the DDX,
as well as moving a bit of transform logic from DDX to DIX.
---
hw/xfree86/modes/xf86Crtc.c|4 +
hw/xfree86/modes/xf86RandR12.c |3 +
hw/xfree86/modes/xf86Rotate.c | 212 +---
Dereferencing the NULL mode pointer would cause a crash. As these transform
matrices won't be used while the CRTC is disabled, just leave their values
alone.
---
randr/rrcrtc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/randr/rrcrtc.c b/randr/rrcrtc.c
index
Doing projective transforms required repositioning the cursor using the
hotspot, but that requires relocating the upper left corner in terms of said
hotspot.
---
hw/xfree86/modes/xf86Cursors.c | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git
---
randr/rrtransform.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/randr/rrtransform.c b/randr/rrtransform.c
index f9934d7..836a7ae 100644
--- a/randr/rrtransform.c
+++ b/randr/rrtransform.c
@@ -20,6 +20,7 @@
* OF THIS SOFTWARE.
*/
+#include randrstr.h
RandR matrix computations lose too much precision in fixed point;
computations using the inverted matrix can be as much as 10 pixels off.
Convert them to double precision values and pass those around. These API
changes are fairly heavyweight; the official Render interface remains fixed
point, so
When the transform management was moved from randrstr.h, the associated
header file became necessary to build drivers. Include it as a part of the
sdk headers.
---
randr/Makefile.am |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/randr/Makefile.am b/randr/Makefile.am
PictureTransformBounds can fail, when this happens, damage the entire screen
so that the shadow gets repainted correctly.
---
hw/xfree86/modes/xf86Rotate.c | 49 +
render/matrix.c |7 +++--
render/picturestr.h |2 +-
3
Create new RRTransform datatype to hold all of the transform related
information, use that in lots of places to pass filters around.
---
hw/xfree86/modes/xf86Crtc.h |3 +
hw/xfree86/modes/xf86Rotate.c | 31 +-
randr/randrstr.h | 27 +++--
randr/rrcrtc.c|
---
randr/randrstr.h |2 ++
randr/rrcrtc.c | 28 ++--
2 files changed, 20 insertions(+), 10 deletions(-)
diff --git a/randr/randrstr.h b/randr/randrstr.h
index cdaebe9..17d0a8b 100644
--- a/randr/randrstr.h
+++ b/randr/randrstr.h
@@ -111,6 +111,8 @@ struct
This width/height value lets filter users know how far the filter spreads
into the source image.
---
render/filter.c | 27 ---
render/picturestr.h |8 ++--
2 files changed, 26 insertions(+), 9 deletions(-)
diff --git a/render/filter.c b/render/filter.c
index
---
hw/xfree86/modes/xf86Crtc.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/hw/xfree86/modes/xf86Crtc.c b/hw/xfree86/modes/xf86Crtc.c
index a40bf18..35c1190 100644
--- a/hw/xfree86/modes/xf86Crtc.c
+++ b/hw/xfree86/modes/xf86Crtc.c
@@ -103,6 +103,16 @@
---
render/filter.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/render/filter.c b/render/filter.c
index b5bcf02..21eedca 100644
--- a/render/filter.c
+++ b/render/filter.c
@@ -252,7 +252,7 @@ PictureSetDefaultFilters (ScreenPtr pScreen)
return FALSE;
This reduces the matrix representation error after inverting a
transformation matrix (although it doesn't eliminate it entirely).
Perhaps we should extend Render to include 64-bit floating point transforms...
---
render/matrix.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
The obvious matrix inversion function, coded using doubles to avoid fiddling
with fixed point precision adventures.
---
render/matrix.c | 80 +++
render/picturestr.h |3 ++
2 files changed, 83 insertions(+), 0 deletions(-)
diff --git
Add APIs to xf86RandR12 support and randr extension to record whether the
driver supports transforms, report that value in the RRGetCrtcTransform
reply.
---
hw/xfree86/modes/xf86Crtc.c|6 ++
hw/xfree86/modes/xf86RandR12.c | 25 +
Need to compute and save the global transform when the driver changes it.
---
randr/rrcrtc.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/randr/rrcrtc.c b/randr/rrcrtc.c
index 1b6350e..c237f03 100644
--- a/randr/rrcrtc.c
+++ b/randr/rrcrtc.c
@@ -233,6 +233,15
Track curent transform down in the mode setting code so that it may be set
separately from RandR.
---
hw/xfree86/modes/xf86Crtc.c| 56 ---
hw/xfree86/modes/xf86Crtc.h| 11 +++-
hw/xfree86/modes/xf86RandR12.c | 36 +
---
hw/xfree86/modes/xf86Crtc.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/hw/xfree86/modes/xf86Crtc.c b/hw/xfree86/modes/xf86Crtc.c
index 9d13898..e153227 100644
--- a/hw/xfree86/modes/xf86Crtc.c
+++ b/hw/xfree86/modes/xf86Crtc.c
@@ -271,7 +271,10 @@
Hi,
Perhaps we should extend Render to include 64-bit floating point transforms...
That would be really great.
I am doing some tricks with mask-transformations having quite a hard
time by the fixed-point limitations, especially for large scales (like
100x).
- Clemens
On Fri, 2008-11-14 at 23:31 +0100, Clemens Eisserer wrote:
Hi,
Perhaps we should extend Render to include 64-bit floating point
transforms...
That would be really great.
I am doing some tricks with mask-transformations having quite a hard
time by the fixed-point limitations, especially
I'm not quite sure what causes it,
TRACE: RADEONPrepareCopyCP
TRACE: RADEONDoneCopyCP
copy without emission
Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812b9ab]
1: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7c45353]
2: /usr/lib/xorg/modules//libexa.so(exaCopyNtoN+0x835)
50 matches
Mail list logo