Hi Valter,
I had this problem long ago with a very similar configuration. It
vanished when Alex Deucher modified some details (like rounding) in the
Radeon mode setting/calculation code.
I don't know about the details, but maybe you can copy the modeline
generated by the proprietary driver and
The integration of the code has some deficiencies which try to resolve here
mainly to make reuse of the code easier. Also, the new valuator masks are
now used by acceleartion, making things much more straightforward.
___
xorg@lists.freedesktop.org:
On 12/09/2010 01:22 AM, Peter Hutterer wrote:
What can be done?
commit beea2378f142556471c62290e275935af848e137
Author: Peter Hutterer peter.hutte...@who-t.net
Date: Mon Dec 6 14:33:43 2010 +1000
xfree86: don't overwrite option list (#32115)
Options set in the
On 11/25/2010 07:42 AM, Joel Feiner wrote:
On Wed, Nov 24, 2010 at 5:44 PM, Simon Thum simon.t...@gmx.de wrote:
On 11/23/2010 06:33 AM, Joel Feiner wrote:
Mouse acceleration seems to have gone away as of a week or so ago. I'm
not
sure which component did it and I don't recall when
On 11/23/2010 06:33 AM, Joel Feiner wrote:
Mouse acceleration seems to have gone away as of a week or so ago. I'm not
sure which component did it and I don't recall when it actually changed
since I use Linux now irregularly and only update once in a while.
Yes, It's a known problem originating
, walt wrote:
On 11/14/2010 09:11 AM, Simon Thum wrote:
Hi all,
yesterday I recompiled xorg, updating from a ca. 3 week old install
using gentoo's live ebuilds. I went into an amusing bug which I narrowed
down a bit.
I'm having the following xorg.conf.d fragment:
Section InputClass
On 11/05/10 00:21, Peter Hutterer wrote:
On Thu, Nov 04, 2010 at 10:35:29PM +1100, Russell Shaw wrote:
In XInput2, when i get a XI_HierarchyChanged event after plugging in
another mouse, is there a way to get a unique identifier for each device
such as a brand and model number?
no, the
Am 21.06.2010 01:53, schrieb Peter Hutterer:
On Sat, Jun 19, 2010 at 07:17:52PM +0200, Harald Dunkel wrote:
AngleOffset is a mousedrv(4) parameter, evdev doesn't have anything
similar and your device is now handled by evdev. Feel free to port this
over.
I've been hoping to somehow unify
default value initialization.
Re-use width/height variables.
Require server 1.6 or later.
synclient: allow Min|MaxSpeed values of 1.0.
Purge GuestMouse support.
Bump to 1.2.99.1.
Simon Thum (4):
Setup pointer acceleration for synaptics
Setup pointer
Am 09.06.2010 00:20, schrieb Jacek Wielemborek:
Hi,
I recently decided to try and build an app allowing me to easily
convert my netbook into an e-book reader at any time. The problem is,
when I try to rotate the screen on the right, making the resolution
600x1024, the touchpad behaves in
Am 14.05.2010 19:37, schrieb Dan Nicholson:
On Thu, May 13, 2010 at 11:45 PM, Nikos Chantziaras rea...@arcor.de wrote:
merge key=input.x11_options.FilterHalflife type=string5/merge
merge key=input.x11_options.FilterChainProgression
type=string2/merge
merge
Am 28.04.2010 02:01, schrieb Peter Hutterer:
sysfs files are for knobs exposed by the kernel.
Simple question, asking for the current way to configure:
How do I speed up my terribly slow TrackPoint?
Simon, do we have anything to speed up devices? looks like everything we
have is to
Am 28.04.2010 13:20, schrieb Tobias Wolf:
On Wed, 2010-04-28 at 11:44 +0200, Simon Thum wrote:
This intends to preserve precision. I'd bet any speed gains one may have
under another OS is driver magic.
I never used this machine under another OS and am not sure how
responsive
Hi Max,
I've had a small look at your work. I've often had requests to do this
by users who assumed this would work the same way as pointer
acceleration, which unfortunately it doesn't. So I have a small comment
and a suggestion.
The comment first; from your rationale: The new event would
Am 16.03.2010 09:42, schrieb Zhang, Xing Z:
Hi experts:
From xlib manual, here are sentences for color:
GrayScale is treated the same way as PseudoColor except that the *primary*
that drives the
screen is undefined. Thus, the client should always store the same value for
red,
Julien Cristau wrote:
This is also expected at the moment. The enumeration of devices gives
us /dev/input/event* (which evdev can handle), and
/dev/input/{mouse,kbd}* (which it doesn't). This results in a couple
error messages for the latter. It should be possible to tone those down
so
Hi all,
I just upgraded my X to use udev. It generally went fine, but I noticed
two minor issues:
At first, the device names have quotation marks. As in
xinput list
...
⎜ ImExPS/2 Logitech Wheel Mouse id=7[slave pointer
(2)]
I looked up the source, but found nothing
Zhi Li wrote:
All,
I'm working in a project which study energy saving on PCs. I saw a
strange thing which was opposite to my intuition: when PC working on
graphic mode, it would be more energy saving.
When in graphic mode, on my PC, it is 52w; when I switched to terminal
mode(on linux
that one in. We'll
see if we get positive feedback.
Yay! Attached.
Cheers,
Simon
From 76ea8499aa308ad535f499cc1e6712dd1ea82373 Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Wed, 9 Sep 2009 14:41:08 +0200
Subject: [PATCH] Setup pointer acceleration for synaptics
Setup dix
Marco Cavallini wrote:
Hi,
I'm testing and debugging xinput-calibrator and looks like
CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored
by Xorg.
Properties may reject attempts to change their value (to specific
values). Also, if the properties don't exist before, you may
Marco Cavallini wrote:
Simon Thum ha scritto, Il 27/01/2010 11:47:
Marco Cavallini wrote:
Hi,
I'm testing and debugging xinput-calibrator and looks like
CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored
by Xorg.
Properties may reject attempts to change their value
0c30a80cb0e32b89a93c2497ebd7ef97652cf211 Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Wed, 9 Sep 2009 14:41:08 +0200
Subject: [PATCH] Setup pointer acceleration for synaptics
Setup dix pointer accel from the synaptics driver so synaptics devices
behave like before while benefiting from dix
Peter Hutterer wrote:
The ususal 5 week schedule will be maintained for 1.7.5
Hi Peter,
since you intend to push 1.7.5, maybe you can include my first ptr accel
xorg.conf.man changes along with fenando's corrections? I hope this
lessens the chance of ppl wasting time with evdev scaling patches
Peter Hutterer wrote:
thanks, that woke me up. I was struggling this morning :)
always a pleasure.
I don't think this is necessary. We're nitpicking on the wording here and
given the number of languages out there there's always going to be some
ambiguity. with this patch you're breaking user
Those patches should address the issues. The rename is skipped for now.
Peter Hutterer wrote:
thanks, that woke me up. I was struggling this morning :)
On Tue, Jan 05, 2010 at 09:13:47PM +0100, Simon Thum wrote:
another round of ptr accel patches. I didn't send to the dev list to
maybe
changes are bogus, I just copied around
and I seem not to have broken things.
Cheers,
Simon
From 6bdb4ab5abef8a2155df23281c4ca1268dc999ae Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Tue, 5 Jan 2010 11:50:05 +0100
Subject: [PATCH 1/4] dix: rename input property for 'constant
Keith Packard wrote:
Do we have enough info to start assigning default profiles to different
kinds of devices yet? Should we stick this in some default xorg.conf.d
fragments? Or should we stick it in the code instead?
Essentially, there is no fixed relation. I tested the 'wacom' profile
w/my
Peter Hutterer wrote:
On Sat, Dec 19, 2009 at 02:25:16PM +0100, Simon Thum wrote:
Peter Hutterer wrote:
given the two changes alan already suggested,
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
please send out the last version of these patches and I'll push them once
they're in my
Lorenz Ruhmann wrote:
After alternating between the two schemes several times and repeating
specific mouse strokes a few dozen times, I'm getting less and less
convinced that there actually is a difference. Also, considering you say
my settings are correct (I'm not using adaptive
Gene Heskett wrote:
On Saturday 19 December 2009, Simon Thum wrote:
Gene Heskett wrote:
I would tend to agree. With modern high resolution mice, I have often
wished I could set the gain to a below 1 condition. My mouse now uses
about a 1 x1.35 area of the pad, to cover a 1680x1250 screen
Justin Piszcz wrote:
On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
Is there a way to exactly reproduce this old behavior with the new code?
I don't like to rely on a scheme that is kinda considered obsolete.
[..]
Yes, this is VERY annoying to me as well (all of the new acceleration
methods
Gene Heskett wrote:
I would tend to agree. With modern high resolution mice, I have often wished
I could set the gain to a below 1 condition. My mouse now uses about a 1
x1.35 area of the pad, to cover a 1680x1250 screen, so its way too fast for
this user.
I'm not sure I got it. What you
Resending to include philip as xinput maintainer. xset doesn't have a
dedicated maintainer. Alan?
Peter Hutterer wrote:
On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
Peter Hutterer wrote:
On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thum wrote:
+has more detials
Peter Hutterer wrote:
On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
Peter Hutterer wrote:
On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thum wrote:
+has more detials. For X.org 1.7
^^^ typo ^^ X.Org X Server 1.7
I missed that one. Our canonical writing
Ross Vandegrift wrote:
When I installed xinput, the first thing I did was look at the man
page. But it's nearly useless - all it really does is list how the
commands map onto API functions. I don't know the XInput API, so most
of it doesn't mean anything to me.
I take it the man page is a
ZelluX wrote:
Considering such a situation, some applications are running on x window
systems and one of them, for example, a web browser has the focus. If there
comes an interrupt, such as a keyboard interrupt, and now kernel takes over
the control. My question is that what's the running
of information.
In general, is it reasonable to point to the wiki from a man page? That
one's separate if the answer is no.
Cheers,
Simon
From 84ceba932e93c0b2467be696c9878c4d9c59312b Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Sun, 18 Oct 2009 15:10:56 +0200
Subject: [PATCH 1/2
Alan Coopersmith wrote:
misunderstanding. (My employer on the other hand, requires us not to
automatically label everything as confidential, since that just causes people
to assume nothing really is, and destroys all value of true confidential
labels.)
I'm amazed by the sheer amount of
Magnus Kessler wrote:
On Friday 06 November 2009, Simon Thum wrote:
Rémi Cardona wrote:
from git and completely rebuilt. And with a single command, users can
rebuild all live packages.
Would you be so kind to explain what exactly you're talking about? I'd
be highly interested...
(Last time
Yotam Medini wrote:
+ On current Ubuntu, it is not easy to configure. The GSynapyics tool
warns (and requires(?)) settings in /etc/X11/xorg.conf
while current configuration happens under /usr/share/hal/fdi/...
I can't say that about ubuntu, but I can place stuff in /etc/hal/fdi/...
so once
Justin Piszcz wrote:
Solution for now as I need a working desktop:
1. Recover OS from backup before upgrade:
2. Pin kde* and xorg* so they are not upgraded anymore.
In the future/if someone from xorg can respond-- is there a fix/way to
make the semantics such that 'xset m 20/5 1' is the
Flittigs at PICT wrote:
Hello all, we are undergrad students trying to install and compile the
latest X release on a virtual box. We did all installation on /opt/MPX
prefix.
on doing sudo /opt/MPX/bin/X -config /../xorg.conf , the X server starts
running and screen goes blank. We also
It's never worked ! I'm using Mandriva One 2009 with KDE 4.2.4, Somehow I had
the
impression it was something to do with the X-server because the
Ctrl-Alt-Bkspace
was also disabled. I have that fixed thanks to the list.
I'll poke around some with the settings and see if I find anything
Maybe different ~/.fonts.config?
Comparing outputs of fc-list may also help.
Giacomo wrote:
Hi to all.
I am Giacomo S. from Elettra synchrotron radiation facility, Trieste, Italy.
We use to develop Qt GUIs on a kubuntu system.
The development process is as follows:
1. develop the
Harald Braumann wrote:
If it's not possible yet, are there plans to implement such
functionality in the X server? Like sending an event whenever the
pointer stops?
Well, X is in pretty much the same situation here; it just knows when
the mouse moves, or when it did so last time (plus something
Peter Hutterer wrote:
XI 1 gives you access to the valuators as well, so this should work in
principle if you register for DeviceButtonPress and friends.
Ok, big sorry if I'm wrong, but to clarify: untranslated valuators are
stored in valuators.data_raw, which is picked up solely by
Florian Echtler wrote:
Hello everyone,
I've recently written an input event driver for a touchscreen, and it's
working out-of-the box with the evdev driver. However, the scaling is a
bit off, so I'd like to do a four-point calibration and set the Evdev
Axis Calibration property accordingly.
Michel Dänzer wrote:
On Fri, 2009-07-10 at 08:51 -0700, Sebastian Glita wrote:
Xorg: pixman-region.c:372: pixman_region_copy: Assertion
`pixman_region_selfcheck (src)' failed.
See http://bugs.freedesktop.org/show_bug.cgi?id=22642 .
Thanks for the pointer! I started rebuilding half my system
Peter Hutterer wrote:
On Sat, Jul 04, 2009 at 02:32:09PM +0200, Simon Thum wrote:
Asbjørn Sannes wrote:
But for Evdev Axis Calibration I have not found anything that works ..
Any hints and suggestions are welcome :)
One could probably do a patch which adds property manipulation to
config
Asbjørn Sannes wrote:
But for Evdev Axis Calibration I have not found anything that works ..
Any hints and suggestions are welcome :)
One could probably do a patch which adds property manipulation to
config/hal, but it didn't surface yet.
I remember to have heard hal can be configured to
jspran...@awlship.com wrote:
Trying to build Kdrive and I receiving the following errors:
kinput.c: In function ‘KdEnableInput’:
kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from
incompatible pointer type
kinput.c: In function ‘KdQueueEvent’:
kinput.c:1675: warning:
Peter Hutterer wrote:
this code hasn't been touched for ages (it's even disabled by default).
hal.c came after this code, so the use of RemoveDevice is more legacy than
anything else.
Have you tried DIDR? Does it work fine? If so I'll just amend your patch
before pushing.
Not really tried
of RemoveDevice(). Daniel, is there a specific reason to use RD
and not DIDR?
Cheers,
Simon
From d2c7f41cc2564b155a285d10f404818410b92e3c Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Fri, 5 Jun 2009 19:14:48 +0200
Subject: [PATCH] config: adapt to Xi2 changes
---
config/dbus.c |2
Peter Hutterer wrote:
On Fri, May 29, 2009 at 03:42:02PM +0200, Simon Thum wrote:
I wonder if one couldn't just do a Xi1 XOpenDevice() to 'convert'
Id-Device* ? Any known reasons?
I'm not sure I understand what you mean, but
- XOpenDevice() is an XI 1 call and I really encourage
Peter Hutterer wrote:
The protocol only cares about the device id, so to make XTest XI2 aware, all
that's needed is some libXtst functions that take an id directly instead of
the XDevice*. So it's a pure client-side change in the library, feel free to
send me the patch :)
I wonder if one
Christian Beier wrote:
Hi there,
with the merge of xi2 coming next week, I wonder what the status of
XTest with xi2 is. Right now, XTest still pretty much looks like XI
1.x, with Device*'s instead of devive ids
(http://cgit.freedesktop.org/xorg/proto/xextproto/tree/XTest.h).
Looking at the
Evgeny M. Zubok wrote:
I have S3 Trio64V2 with VBE 1.2 and I want to add the possibility of
display autodetection via DDC to s3 driver. There is two ways to deal
with DDC: (i) VESA BIOS Extension and (ii) directly from videochip's DDC
registers. The later method currently is impossible to
Damien Mir wrote:
Hello,
I recently installed Opensuse 11.1 on a HP Pavilion dv8000 ( with XPRESS
200M graphics ), shipped with Xorg 7.4
(--) RADEON(0): Chipset: ATI Radeon XPRESS 200M 5955 (PCIE) (ChipID =
0x5955)
I am experiencing some kind of slow 2D performance, never seen before on
Peter Hutterer wrote:
On Sat, Apr 18, 2009 at 10:54:31AM +0200, Florian Echtler wrote:
However, the second one (controlled by touchpad) reports values in the
range (1472,1408) to (5472,4448). This is also reported in the Xorg.log
by the synaptics driver. How can I map these to screen
Peter Hutterer wrote:
relative to the window's origin but in the screen coordinate system.
so if the window is on 100/100, a device on root 101/101 has event 1/1,
even if the valuator state is e.g. 7202/2381 (valuators are in device
coordinates).
Thanks for the clarification.
Cheers,
Florian Echtler wrote:
However, the second one (controlled by touchpad) reports values in the
range (1472,1408) to (5472,4448). This is also reported in the Xorg.log
by the synaptics driver. How can I map these to screen coordinates? As
the pointer still moves in screen coordinates, the
Harald Dunkel wrote:
Sorry, but I do want to skip pixels (for gaming only, as written
before). I understand that somebody overloaded (abused?)
threshold = 0 to provide a completely different acceleration
characteristic. I would like to have the classic profile with
a simple characteristic and
Hi,
you may want to read this:
http://www.x.org/wiki/Development/Documentation/PointerAcceleration
It is geared towards development, but also contains a lot of end-user
info as well.
with a constant acceleration (e.g. for gaming)? Something like
I'm not sure what you mean by 'constant
Alan Coopersmith wrote:
Is there any reason we should have two forks of this? Which one
do most distros ship?
On gentoo:
[I] x11-apps/luit
[...]
Homepage:http://xorg.freedesktop.org/
Not a proof, though.
___
xorg mailing list
This cannot be deduced from that line. You need to review your math.
On Wednesday 08 April 2009 22:52:12 Thomas Dickey wrote:
Behdad's comment doesn't make sense in English.
(Perhaps someone can help Behdad with that - or else explain to him
what API-stable might mean).
It makes perfect
Tuomo Valkonen wrote:
The only problem with core fonts is the blur-fascist elite
not bothering to fix UTF-8 fontset support, so there you have
some problems.
If transporting visual information that would otherwise go lost is
blurring, then I'm probably not from this world. The implementation
Rémi Cardona wrote:
Le 27/03/2009 19:55, Simon Thum a écrit :
Hi,
I'm bitten by this issue too and I'm somewhat lost with this. The patch
has not yet been applied or commented on xorg, so I just want to make
sure it's seen.
Then render.h also needs something like this...
To quote from
Hi,
I'm bitten by this issue too and I'm somewhat lost with this. The patch
has not yet been applied or commented on xorg, so I just want to make
sure it's seen.
8yrgr4dkp...@dyweni.com wrote:
Just noticed that I created the reverse patch. Here to correct one.
Hey Everyone,
I found a
I did a quick sysprof test while switching desktops, and it looks like
it's all in memcpy:
miClearToBackground 0.00 77.45
miPaintWindow 0.00 77.45
ValidateGC
Jeremy C. Reed wrote:
On Wed, 18 Mar 2009, Peter Hutterer wrote:
I think in 1.4, xf86OSMouseInit was still in the server, so maybe
there's some conflicts there.
That sounds like that was it. Maybe the xf86-input-mouse configure should
check for xorg-server = 1.4.99.something instead of =
Halim Issa wrote:
Would I be correct to assume that the best way to work around this is to
downgrade while waiting for these issues to stabilize upstream in the next
few months?
Depends on how whacky you want to go. E.g. on LSF/non-production I'd
give remi's script (see bug) a try. Worked
Bill Crawford wrote:
included on the command line at link time. Libtool sort of abstracts this,
but
to do so it needs to keep track of what those dependencies are, and does so
by
storing them in this .la file.
Thanks for the explanation. What baffles me is that AFAICT this
introduces a
Halim Issa wrote:
grep: /usr/lib/libxcb-xlib.la: No such file or directory
/bin/sed: can't read /usr/lib/libxcb-xlib.la: No such file or directory
libtool: link: `/usr/lib/libxcb-xlib.la' is not a valid libtool archive
Possibly, this is biting you:
http://bugs.gentoo.org/show_bug.cgi?id=158476
James Cloos wrote:
The Video Bus input device is a keyboard. Mine is:
...
So, if one wants to handle those keys via X, evdev needs to read that
input device.
Thanks! I almost had managed to spend a whole day without learning
something new...
Cheers,
Simon
Dan Nicholson wrote:
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
...
That an awful lot. on my system, only keyboard and pointer are listed.
Try booting an older kernel, upgrading HAL, throw out any home-brew HAL
fdi's or go to the HAL list.
No, I think that's typical
Ben Gamari wrote:
On 03/11/2009 11:28 AM, Simon Thum wrote:
lshal | grep -10 x11_driver
might be valuable.
Your wish is my command:
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
...
That an awful lot. on my system, only keyboard and pointer are listed.
Try booting
Ben Gamari wrote:
be too difficult to implement. Am I wrong? If not, I could potentially
take a stab at it.
Oh, I overlooked that one earlier. In the docs to ptr accel I've
described how to detect whether the server is configured to do
predictable pointer accel. The job would be defeating
Peter Hutterer wrote:
yeah, of course. sorry. what I meant was that the value x is sent as x * (1
16). A little test program for random values between 0 and 0x showed an
average rounding error of 0x08.
I can't judge whether that is good or bad :)
IMO for the protocol, definition is
Carl Karsten wrote:
http://dpaste.com/1931/
xorg finds and uses the touchscreen - good.
I need to set min/Max X/Y values - I am lost on how to do that. the #ed out
parts either have 0 effect or disable it - mouse doesn't move when I touch.
#Option MinX 4100
#Option
Dirk wrote:
I was referring to reading /many/ manuals as a relic of the nineties.
Oh, I got that, I just used it as a starter :)
I'll try this on another machine as soon as it is in debian/unstable (if
not already)... It would be great it this works and can't be overriden
by anything.
If you
Pedro Izecksohn wrote:
On 2/24/09, Simon Thum simon.t...@gmx.de wrote:
Pedro Izecksohn wrote:
Where it may be found?
Nowhere, AFAIK.
You may want to know this: http://bugs.gentoo.org/show_bug.cgi?id=158476
First off, you need to use reply-all. It's an incident I saw this.
Let see if I
Peter Hutterer wrote:
XML is merely a container format. It doesn't solve our actual problem - what
information to send to the client.
[...]
We're in pretty unchartered territory, with much of the UI needing to change
anyway to accommodate for all this. Once the UI changes, the information need
Pedro Izecksohn wrote:
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
Same here, on my local system (gentoo + X11 overlay). In my git tree it
gives a good-looking -I arg.
Though I never had problems building anything.
Simon Thum wrote:
Pedro Izecksohn wrote:
pkg-config --cflags xproto
prints a line-feed only and keysymdef.h exists in my system and it is in
the right place.
Same here, on my local system (gentoo + X11 overlay). In my git tree it
gives a good-looking -I arg.
Sorry for the noise. I haven't
Bill Crawford wrote:
In theory a lot of them shouldn't need to, because they're installed in a
subdirectory of /usr/include, and you're intended to include
libfoo/blah.h ...
I guessed that also, but couldn' get it nailed down. Anyway, it looks
more like the OP's script is broken.
Hi,
I've just rebuilt my system's ati driver, and now it's missing the
'coherent_mode' RandR prop.
This might be correct, as I only abused this prop to reinit stuff until
my display stopped showing blackouts (happens from time to time, so this
saves me restarting xorg).
In case this is
Soeren Sandmann wrote:
Simon Thum simon.t...@gmx.de writes:
However, when you implement super sampling with respect to gamma, the
quality loss drops to nearly zero. I'd say typically you need no more
strange higher quality filters when that's done.
Even a simple non-gamma-correct
Hello,
I just had my LCD tell me something like the mode should not exceed
1280x1...@75. This happened directly after starting X, and it was the
only occurrence this year, so nothing serious. However, I killed X,
restarted it and diffed the logs:
(II) RADEON(0): [agp] Ring mapped at 0xb7b2f000
Peter Hutterer wrote:
Thanks for the comments. All your suggestions have been added, but I'll
refrain from commenting on them much (the spec has to work on it's own
eventually).
No prob. Some details follow though.
FP1616
-Fixed point decimal in 16.16 format as 32 bit integer. The
Peter Hutterer wrote:
FP1616
Fixed point decimal in 16.16 format as 32 bit integer. The client is
required to convert to 16.16 decimal format.
Maybe it's just me, but I don't really get what 16.16 decimal format
means.
┌───
XIChangeDeviceHierarchy
Hi Peter,
looks pretty good to me.
One tiny nit however: E.g. in eventconvert.c there are switch statements
which go like
switch(EventType){
...big list of labels for one thing...: do it; break;
}
So essentially, I guess, you're checking for some commonality, or
property. Centralizing such
Peter Hutterer wrote:
patches welcome :)
Here y'r. :)
From e25f0f7c38c9f5d5cfab4a20fe42ee5cbf38d012 Mon Sep 17 00:00:00 2001
From: Simon Thum simon.t...@gmx.de
Date: Fri, 23 Jan 2009 11:39:56 +0100
Subject: [PATCH] xinput: create well-known atoms on demand, rather than preinit
them
---
Xi
Hi Peter,
some rants from me:
┌───
XIDeviceHierarchyEvent:
GENERICEVENTDATA
flags: SETofHIERARCHYMASK
ndevices: CARD16
───
devices:LISTofINT16
└───
On XDS 08, Keith suggested simply putting them on the wire. That is,
require IEEE756 32 bit and account for endianness.
GLX already uses both 32 and 64 bit IEEE floats on the wire, so I don't
see any reason to use something different here.
I'd like to add floats to the render protocol as
Hello people,
I'm trying to get some consensus about floats on the wire. I cc'ed some
who spoke about the issue on the list in a non-exhaustive search.
Recap: Peter and I want to transfer floats in input properties, see there:
http://lists.freedesktop.org/archives/xorg/2008-December/041647.html
Walter Harms wrote:
if floats are realy needed i would go with an already established like XDR
it is already in glibc and it is a defined RFC.
Well, XDR simply states to use the IEEE representation. So I take this
as one more vote for IEEE.
At the XDR level, there seems to be an incompatibility
Alex Deucher wrote:
On Thu, Nov 13, 2008 at 7:54 AM, Simon Thum [EMAIL PROTECTED] wrote:
Gene Heskett wrote:
But its not that simple either, cuz when running the radeon driver, I get
random screen blanking for 1-10 seconds at a time, and for a change it
doesn't seem to be tied to the time
Jeremy Huddleston wrote:
-unsigned int oldtail = miEventQueue.tail, newtail;
+unsigned int oldtail = miEventQueue.tail;
All fine, but is there a specific reason to remove newtail? Not that I'd
expect this to save more than one or two cycles on any platform...
Gene Heskett wrote:
But its not that simple either, cuz when running the radeon driver, I get
random screen blanking for 1-10 seconds at a time, and for a change it
doesn't seem to be tied to the time of day since its doing it right now and
it is 10 pm.
I'm experiencing the exact same
Matthieu Herrb wrote:
Simon Thum wrote:
Tiago Vignatti wrote:
http://www.nongnu.org/avr-libc/user-manual/group__util__atomic.html
Does we have this kind of thing in C libraries? It would be useful.
If I got it right, that's posix + pthreads functionality specialized for
an amtel platform
1 - 100 of 123 matches
Mail list logo
