Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/xorg/gtest/evemu/xorg-gtest-device.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/xorg/gtest/evemu/xorg-gtest-device.h
b/include/xorg/gtest/evemu/xorg-gtest-device.h
index 35e5459..223738e
Fix compilation on systems that don't provide O_CLOEXEC.
I wonder if it will work as intended, or if more is needed.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info:
Looking good!
Signed-off-by: Simon Schubert 2...@0x2c.or
thanks,
simon
On 08/12/2012 06:40 PM, Matt Turner wrote:
From: Simon Schubert 2...@0x2c.org
When fbBresSolid draws a line, it can happen that after the last
pixel, the Bresenham error term overflows, and fbBresSolid paints
another
On Mon, Aug 13, 2012 at 12:40 AM, Matt Turner matts...@gmail.com wrote:
Mitch, can I get a Tested-by tag?
Well including that patch certainly stopped the crashes for me at the
time. So for that reason I'm happy to say:
Tested-by: Mitch Davis mjd+freedesktop@afork.com
However I have to
On 08/12/12 11:07 PM, Aaron.Chen 陈俊杰 wrote:
I didn't found this mail show up on the xorg-devel mail list and there is no
response. Maybe it didn't sent successfully, so I sent it again.
2.2 MB mails require moderator approval to be sent to the mailing list.
Please don't send multiple copies
On 08/09/2012 10:38 PM, Peter Hutterer wrote:
Add a set of basic states to Process to allow callers to keep track of which
state a process is in (as seen from the library). This simplifies code that
needs to happen on certain conditions only, e.g. log file cleanup is only
needed if the process
On 08/09/2012 10:38 PM, Peter Hutterer wrote:
Simple unlink() call to the logfile in use. The log file is only removed if
the server was started and terminated successfully. If it was never started
or the startup failed for some reason, this function does nothing.
Signed-off-by: Peter Hutterer
On 08/09/2012 10:38 PM, Peter Hutterer wrote:
A GetOption() call would be more generic here, but for log and config file
it's more intuitive to have actual methods instead of having to pass
-config to a generic GetOption() call.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
On 08/09/2012 10:38 PM, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/xorg/gtest/xorg-gtest-xserver.h | 1 +
src/xserver.cpp | 6 ++
2 files changed, 7 insertions(+)
diff --git a/include/xorg/gtest/xorg-gtest-xserver.h
On 08/12/2012 11:26 PM, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/xorg/gtest/evemu/xorg-gtest-device.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/xorg/gtest/evemu/xorg-gtest-device.h
Matt Turner matts...@gmail.com writes:
From: Simon Schubert 2...@0x2c.org
When fbBresSolid draws a line, it can happen that after the last
pixel, the Bresenham error term overflows, and fbBresSolid paints
another pixel before adjusting the error term.
However, if this happens on the last
I submitted this patch a couple of weeks ago but didn't get a reply (maybe
because I omitted the evdev label from the subject line). So here it is
again, now rebased atop 5af11b6 (latest on master).
Note that Daniel Stone said on 11 March 2008: IMO this should be kernelside,
though it's
This patch adds one configuration option, DebounceDelay, and one XInput
property, Evdev Debounce Delay. They refer to the amount of time to wait
after receiving a mouse button release event from the kernel before posting
the event to the X server. If a mouse button pressed event is received before
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) ). The significant bits of each component
of each
As I understand it: the gamma-correction tables configured through
XRR[GS]etCrtcGamma store 16:16:16 X Colors. An X Color has some number
of significant bits, stored in the MSBs of the X Color (reported
in Visual::bits_per_rgb, though the gamma-correction tables are
visual-independent). The
The gamma-correction lookup table values are 16:16:16 X Colors, where the
MSBs are programmed into the hardware lookup table. Rather than compute
values over the entire range [0,65536) (where values below 2^(16 - sigbits)
will receive the same hardware value), compute values over the range
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
include/xorg/gtest/xorg-gtest-process.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/xorg/gtest/xorg-gtest-process.h
b/include/xorg/gtest/xorg-gtest-process.h
index 69b3b34..8cf60e3 100644
---
17 matches
Mail list logo