They are stored in floats, so we might as well take them like they are. Plus,
this way keith's mouse can be configured to his liking.
Spotted by Keith Packard.
---
hw/xfree86/common/xf86Xinput.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Peter Hutterer wrote:
They are stored in floats, so we might as well take them like they are. Plus,
this way keith's mouse can be configured to his liking.
Ok with me, but for the protocol: I stored them as floats mainly because
I store them reciprocal (to save cycles).
E.g. a deceleartion of
I have a TV monitor with the 1366*768 listed as its native resolution.
I have connected it with dual-head separate X-screens via DVI-HDMI.
However, no matter what resolution I set for the display, a considerable
part of the display is missing around the edges.
The panels becomes hidden below the
Updated series of patches to bring Cygwin/X up to date,
so it at least builds and minimally works
Any comments on their correctness appreciated
Thanks!
--
___
xorg mailing list
xorg@lists.freedesktop.org
---
xserver/hw/xwin/InitOutput.c | 17 -
xserver/hw/xwin/Makefile.am |1 +
2 files changed, 1 insertion(+), 17 deletions(-)
Index: xorg-git/xserver/hw/xwin/InitOutput.c
===
---
---
xserver/hw/xwin/InitInput.c |3 +--
xserver/hw/xwin/winkeybd.c | 20
xserver/hw/xwin/winmouse.c | 25 +++--
3 files changed, 28 insertions(+), 20 deletions(-)
Index: xorg-git/xserver/hw/xwin/InitInput.c
Patch by Yaakov Selkowitz
---
macros/xorg-macros.m4.in |4
1 file changed, 4 insertions(+)
Index: xorg-git/macros/xorg-macros.m4.in
===
--- xorg-git.orig/macros/xorg-macros.m4.in
+++ xorg-git/macros/xorg-macros.m4.in
@@
---
xserver/configure.ac |6 --
xserver/hw/xwin/InitInput.c|7 +++
xserver/hw/xwin/Makefile.am| 19 ++-
xserver/hw/xwin/winerror.c | 11 +--
xserver/hw/xwin/winmultiwindowwm.c |9 +
On Thu, Oct 16, 2008 at 5:02 PM, Michel Dänzer
[EMAIL PROTECTED] wrote:
On Wed, 2008-10-15 at 21:59 +0200, Maarten Maathuis wrote:
On Wed, Oct 15, 2008 at 9:43 PM, Eric Anholt [EMAIL PROTECTED] wrote:
Migrating out for a write-only operation is just broken, and is the
thing that should be
On Wed, 2008-10-15 at 12:55 +1030, Peter Hutterer wrote:
+ /* Set the keyboard to RAW mode. If we're using the keyboard
+ * driver, the driver does it for us. If we have AEI on, then
+ * we're expecting the devices to be added (i.e. evdev) and we
+ * have
On Tue, 2008-10-14 at 21:28 +0100, Andrew Clayton wrote:
On Mon, 13 Oct 2008 17:08:29 -0400, Joel Feiner wrote:
And on that note, how about allowing proper 3d and compositing
acceleration across screen area bigger than 2048x2048 (I believe
that's the limit). It'd be nice to be able to
On Thu, 2008-10-16 at 08:02 -0700, Michel Dänzer wrote:
On Wed, 2008-10-15 at 21:59 +0200, Maarten Maathuis wrote:
On Wed, Oct 15, 2008 at 9:43 PM, Eric Anholt [EMAIL PROTECTED] wrote:
Migrating out for a write-only operation is just broken, and is the
thing that should be fixed there.
Just to satisfy my curiosity, why was it that with MergedFB on radeon
(before randr 1.2) I was able to have full acceleration across two screens?
Was there no scan out limit in that particular case or was there some other
workaround?
On Thu, Oct 16, 2008 at 1:39 PM, Adam Jackson [EMAIL PROTECTED]
On Wed, 2008-10-15 at 22:06 +0200, Pierre Willenbrock wrote:
Hi,
i found randr property changes killed all my gtk applications. Checking
the protocol stream revealed broken sequence numbers for the randr
property events. The attached patch for xserver fixes this. I also added
support for
On Thu, 2008-10-16 at 14:07 -0400, Joel Feiner wrote:
Just to satisfy my curiosity, why was it that with MergedFB on radeon
(before randr 1.2) I was able to have full acceleration across two
screens? Was there no scan out limit in that particular case or was
there some other workaround?
Hi there,
having some trouble with my mouse wheel. The hardware is a MS IntelliMouse
Optical USB.
System is running
xorg-server-1.5.2
xf86-input-evdev-2.0.6
gentoo-sources-2.6.27
hal-0.5.11-r1
The problem: When starting/restarting the xserver the mousewheel does not work.
Investigating with
I think this belong here rather than on [EMAIL PROTECTED]
- Forwarded message from Aaron Plattner [EMAIL PROTECTED] -
From: Aaron Plattner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Xcb] [PATCH] Fix memory leak in _XReply
Date: Wed, 17 Sep 2008 00:27:21 -0700
X-Spam-Status:
On Thu, Oct 16, 2008 at 23:55:25 +0200, Julien Danjou wrote:
I think this belong here rather than on [EMAIL PROTECTED]
That was fixed a while ago, commits
2335eafe4b53c27f6f9ee1bab3e1f5842f896428 and
340422a5c7a413faef18666cada27cee14615250.
Cheers,
Julien
I forced the Xorg to use the VESA driver (tweaked an HSync value)
and 1.5.1 came up on the notebook.
It appears that AGPgart is broken on non-AMD64 Solaris 10.
Pat
---
On Tue, Oct 7, 2008 at 10:55 AM, Pat Kane [EMAIL PROTECTED] wrote:
I am trying to run Xorg 1.5.1 on a Gateway T-6836
On Thu, Oct 16, 2008 at 11:10:39PM +0200, Tobias Jakobi wrote:
The problem: When starting/restarting the xserver the mousewheel does not
work. Investigating with xev reveals that the wheel generates button events
6 and 7.
How to get the mouse working: Unplug and replug the device, then the
Peter Hutterer wrote:
you don't have any button mapping set, do you?
Important part from HAL config:
!-- Microsoft IntelliMouse Optical USB mouse --
device
match key=info.capabilities contains=input.mouse
merge key=input.x11_driver type=stringevdev/merge
merge key=input.device
Julien Cristau (1):
Set pInfo-fd to -1 on DEVICE_CLOSE
Peter Hutterer (3):
Fix Device reopened after N attempts message.
Don't post keycodes 255.
evdev 2.0.7
git tag: xf86-input-evdev-2.0.7
Announcing RC1 of evdev 2.1.
Long overdue, it provides a number of features over the current stable 2.0:
- The driver forces the evdev ruleset and thus allows other xkb models than
evdev to be selected without further repercussions (requires
xkeyboard-config 1.4).
- Mouse wheel emulation
On Thu, Oct 16, 2008 at 01:10:03PM +0100, [EMAIL PROTECTED] wrote:
Apparently we shouldn't need this, something else is wrong...
no, I was wrong in the previous email, confusing the intention of the code
here. Am I right that this is the interface between X and the windows API?
In that case
Julien Cristau (1):
Set pInfo-fd to -1 on DEVICE_CLOSE
Peter Hutterer (3):
Fix Device reopened after N attempts message.
Don't post keycodes 255.
evdev 2.0.7
git tag: xf86-input-evdev-2.0.7
Announcing RC1 of evdev 2.1.
Long overdue, it provides a number of features over the current stable 2.0:
- The driver forces the evdev ruleset and thus allows other xkb models than
evdev to be selected without further repercussions (requires
xkeyboard-config 1.4).
- Mouse wheel emulation
26 matches
Mail list logo
