pInfo-atom was removed in xorg-server-1.9.0-26-g9802cca
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/mouse.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/mouse.c b/src/mouse.c
index c7aa734..5e397ce 100644
--- a/src/mouse.c
+++ b/src/mouse.c
@@
On 08/14/12 11:00 PM, Peter Hutterer wrote:
pInfo-atom was removed in xorg-server-1.9.0-26-g9802cca
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/mouse.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/mouse.c b/src/mouse.c
index
Am 14.08.2012 01:25, schrieb Andy Ritger:
The gamma-correction lookup table managed through XRR[GS]etCrtcGamma is
2^n in size, where 'n' is the number of significant bits in the X Color.
Each element in the gamma-correction lookup table is a 16:16:16 X Color
(i.e., in the range [0,65536) ).
Signed-off-by: Adam Jackson a...@redhat.com
---
hw/xfree86/Makefile.am | 12 ++--
hw/xfree86/int10/Makefile.am |8 ++--
hw/xfree86/vbe/Makefile.am |2 ++
3 files changed, 10 insertions(+), 12 deletions(-)
diff --git a/hw/xfree86/Makefile.am b/hw/xfree86/Makefile.am
On 13 August 2012 16:25, Andy Ritger arit...@nvidia.com wrote:
The gamma-correction lookup table managed through XRR[GS]etCrtcGamma is
2^n in size, where 'n' is the number of significant bits in the X Color.
...
xrandr.c | 15 +++
1 files changed, 11 insertions(+), 4
On Wed, Aug 15, 2012 at 08:55:40AM -0700, walter harms wrote:
Am 14.08.2012 01:25, schrieb Andy Ritger:
The gamma-correction lookup table managed through XRR[GS]etCrtcGamma is
2^n in size, where 'n' is the number of significant bits in the X Color.
Each element in the gamma-correction
On Wed, Aug 15, 2012 at 09:36:58AM -0700, Yang Zhao wrote:
On 13 August 2012 16:25, Andy Ritger arit...@nvidia.com wrote:
The gamma-correction lookup table managed through XRR[GS]etCrtcGamma is
2^n in size, where 'n' is the number of significant bits in the X Color.
...
xrandr.c | 15
The following changes since commit c0540b4c8db676d18a9a09828f1590b0b16f9ebc:
Kludge -- Call RandR screen before cleaning up xf86 crtcs (2012-08-14
17:14:55 -0700)
are available in the git repository at:
git://people.freedesktop.org/~jeremyhu/xserver master
for you to fetch changes up to
XT_FONTPATH has to be a valid font path.
Also trim at least one remote path from XT_FONTPATH_GOOD, so it
isn't the same as XT_FONTPATH.
Signed-off-by: Peter Harris phar...@opentext.com
---
This works well in my setup. Is anyone relying on xtest font directories
being
in the same location on
On 2012-08-03 17:17, Jeremy Huddleston Sequoia wrote:
For the series of 3 patches:
Reviewed-by: Jeremy Huddleston Sequoia jerem...@apple.com
Thanks. Pushed.
Peter Harris
--
Open Text Connectivity Solutions Group
Peter Harris
Paul Berry stereotype...@gmail.com writes:
In __glXScreenInit() we generate the set of GLX visuals in two steps:
first we match each pre-existing X visual with a corresponding
FBConfig, then we generate a new X visual to correspond to all the
remaining FBConfigs.
Merged.
c0540b4..16d8da5
Jeremy Huddleston Sequoia jerem...@apple.com writes:
XQuartz: Fix build regression for GlxExtensionInit (2012-08-15 10:28:16
-0700)
Merged.
16d8da5..ad5fe2d master - master
--
keith.pack...@intel.com
pgpBxL7O62eCT.pgp
Description: PGP signature
Peter Hutterer peter.hutte...@who-t.net writes:
Feel free to calculate what the difference in coordinate systems must be to
favour one of the other :)
Yeah, so when possible, smashing back to known screen coords definitely
seems like the right option :-)
--
keith.pack...@intel.com
The server uses the flags to decide if a device comes up as attached or
floating slave. Overwriting the flag after the server has processed the
CorePointer/AlwaysCore/Floating/etc options results in the device always
coming up as floating slave. This again makes the device appear
unresponsive.
As of 81cfe44b1ed0de84ad1941fe2ca74bebef3fc58d, miPointerSetPosition now
returns the screen pointer of the device. This broke floating slave devices,
as soon as a motion event was submitted, miPointerSetPosition returned NULL,
crashing the server.
dev-coreEvents is only false if the device is a
1/5 is just rearranging, the interesting bits are 3 and 4 to add signed
printing to sigsafe logging.
5/5 changes the current behaviour to allow signal-unsafe logging again. This
is largely done because I won't be able to fix all drivers by 1.13 and given
that we had signal unsafe logging for
Throw an assert when the conversion fails instead of just returning. Asserts
are more informative.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/signal-logging.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/test/signal-logging.c
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/signal-logging.c | 101 ++
1 file changed, 101 insertions(+)
diff --git a/test/signal-logging.c b/test/signal-logging.c
index 6467150..f66f773 100644
--- a/test/signal-logging.c
+++
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/misc.h| 1 +
os/utils.c| 14 +
test/signal-logging.c | 80 +--
3 files changed, 92 insertions(+), 3 deletions(-)
diff --git a/include/misc.h
The mouse driver uses %i in some debug messages
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
os/log.c | 10 ++
test/signal-logging.c | 21 +
2 files changed, 31 insertions(+)
diff --git a/os/log.c b/os/log.c
index 25da9f6..4348739 100644
Throw an error into the log file, but continue anyway. And after three
warnings, stop complaining. Not all input drivers will be fixed in time (or
ever) and our printf implementation is vastly inferior, so there is still a
use-case for non-sigsafe logging.
This also adds more linebreaks to the
On Wed, Aug 15, 2012 at 12:36:39PM -0400, Adam Jackson wrote:
Signed-off-by: Adam Jackson a...@redhat.com
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
Cheers,
Peter
---
hw/xfree86/Makefile.am | 12 ++--
hw/xfree86/int10/Makefile.am |8 ++--
On Fri, Aug 10, 2012 at 01:03:30PM -0400, James M Leddy wrote:
On 08/09/2012 06:16 PM, James Cloos wrote:
We do need to add a keysym for AudioMicMute, but do we want to continue
to (ab)use XF86's keysym region or start a section for these types of
keys in keysymdef.h?
There were some
23 matches
Mail list logo
