Hi all,
I'm digging around at a quirk involving Scroll Lock and KVM switching
that I think X is responsible for and hoping someone here can explain
it. At this point I can work around it myself. But I'd really like to
understand it, or perhaps provoke a change to make it work better for
others
On 01/18/12 03:23 AM, sudeep sagar wrote:
Hi All,
I am having problems on how to compile editres.
This is my first open source project.
Can anybody help me with a doc/steps to help me understand How to compile
editres.
The INSTALL file in the editres tarball should document the build
Hello,
I merged the code from transset-df, did a lot of cleanup and fixed
memory leaks. So I guess that should be fine now, but if anyone is
willing to review, that would be great of course.
What should I do to get it included into xorg/app/? Thanks.
Regards,
--
Arnaud Fontaine
On Tue, Jan 17, 2012 at 10:02 PM, Daniel Stone dan...@fooishbar.org wrote:
indent -linux -bad -bap -blf -bli0 -br -brs -cbi0 -cdw -nce -cs -i4 -hnl
-l80 -lc80 -lp -nbbo -nbc -nbfda -nprs -npcs -npsl -saf -sai -saw -nut
About a dozen of the options you specify are already included in the
-linux
A consistent coding style is a Good Thing™.
Trevor’s comments should be addressed.
The final indent command should be documented not only in the commit log
but also in a README file. That should help encourage those who submit
patches based on the tar releases also to maintain the resulting
On Tue, Jan 17, 2012 at 10:02 PM, Daniel Stone dan...@fooishbar.org wrote:
I honestly --
honestly[0] -- don't care what the coding style is. I just care that we
have one.
PS I forgot to add that I agree with this statement 100% and think
this is a good conversation to be having during the
I'm surprised nobody seems interested in this patch, I would have
thought a general mechanism to provide per-component configuration
options would have been a feature for which people would have been
waiting; especially the distribution maintainers.
I was trying to perform a build from the git
On Tue, Jan 17, 2012 at 11:05 PM, Daniel Stone dan...@fooishbar.org wrote:
Hi,
The following commit is available in the 'xaa' branch of
git://people.freedesktop.org/~daniels/xserver - I think the commit
message explains it fairly well.
I've got patches to intel, ati, mach64 and mga to fix
On Wed, Jan 18, 2012 at 03:05:41PM +1100, Daniel Stone wrote:
commit 3811d1b85b71c1f8bd0b3c8269e0f7d388a51c2b
Author: Daniel Stone dan...@fooishbar.org
Date: Wed Jan 18 15:01:09 2012 +1100
Remove XAA
It hasn't worked for over four years. No-one's even come close to
On 12-01-18 11:14 AM, Trevor Woerner wrote:
I'm surprised nobody seems interested in this patch, I would have
thought a general mechanism to provide per-component configuration
options would have been a feature for which people would have been
waiting; especially the distribution maintainers.
On 01/18/12 07:08 AM, James Cloos wrote:
A consistent coding style is a Good Thing™.
Yes.
The final indent command should be documented not only in the commit log
but also in a README file. That should help encourage those who submit
patches based on the tar releases also to maintain the
On 01/17/12 07:02 PM, Daniel Stone wrote:
I'd like to see this merged for 1.12, despite the merge window having
shut, so patches for 1.13's master are more likely to apply to 1.12.
It's arguably not the best time to do it, but there is no good time.
Makes sense to me - no matter when we do it,
On 12-01-16 06:22 PM, Trevor Woerner wrote:
From: Trevor Woerner twoer...@gmail.com
Allow a user to specify per-component configure options by
providing them in the --modfile file. Any text remaining on
a line following a given module/component is assumed to be
options which will be passed
On 01/18/2012 04:02 AM, Daniel Stone wrote:
I'd like to see this merged for 1.12, despite the merge window having
shut, so patches for 1.13's master are more likely to apply to 1.12.
It's arguably not the best time to do it, but there is no good time.
As a downstream that is doing a one-off
On 01/18/2012 04:02 AM, Daniel Stone wrote:
Hi all,
So since the list has been fairly quiet and uncontroversial since the
Ctrl-Alt-Backspace argument, I thought I might throw two comedy patches
out there and see if they stuck.
No but seriously though, it's both a) utterly ridiculous and b)
Thanks for the review Gaetan!
I had completely forgot about the CONFFLAGS option. I'll start again
and integrate the two (or could this be considered a replacement?).
I'll also provide more usage documentation.
___
xorg-devel@lists.x.org: X.Org
Hi Alan,
Thanks for the review.
(Please note that I'm purposefully being overly descriptive to help
others on the list who might be new to the build.sh script)
On Wed, Jan 18, 2012 at 4:09 PM, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
However, I wasn't quite clear on how to use it -
The biggest (only?) downside is that any one-shot an/or on-going
reformatting of _existing_ code confounds future git-annotate and
git-bisect :-(
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info:
On Wed, Jan 18, 2012 at 02:32:48PM -0500, Gaetan Nadon wrote:
On 12-01-16 06:22 PM, Trevor Woerner wrote:
From: Trevor Woerner twoer...@gmail.com
Allow a user to specify per-component configure options by
providing them in the --modfile file. Any text remaining on
a line following a
On Tue, Jan 17, 2012 at 09:26:14PM +0100, Matthieu Herrb wrote:
From: Peter Hutterer peter.hutte...@who-t.net
Calculate length field to a multiples of sizeof(XID). XIDs are typedefs
to ulong and thus may be 8 bytes on some platforms. This can trigger a
SIGBUS if a class ends up not being
Signed-off-by: Chase Douglas chase.doug...@canonical.com
---
dix/getevents.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/dix/getevents.c b/dix/getevents.c
index 2946b16..1547059 100644
--- a/dix/getevents.c
+++ b/dix/getevents.c
@@ -1878,9 +1878,13 @@
An indirect touch device, such as a multitouch touchpad, has relative X
and Y axes internally. These axes are in screen coordinates. However,
the cooresponding axes for touch events are in absolute device
coordinates.
Signed-off-by: Chase Douglas chase.doug...@canonical.com
---
dix/getevents.c |
For expediency, it made sense to always have the X and Y axes set for
direct touch device event propagation. The last X and Y values are
stored internally. However, indirect device touch event propagation
does not depend on the touch's X and Y values. Thus, we don't need to
set the values for
Hi,
On 19 January 2012 04:03, Jamey Sharp ja...@minilop.net wrote:
I love this. It invalidates some of my outstanding patches in the best
possible way. But... could you explain (preferably in the commit
message) what evidence you have that it hasn't worked? I thought
people were still using
Hi,
On 19 January 2012 01:11, Trevor Woerner twoer...@gmail.com wrote:
On Tue, Jan 17, 2012 at 10:02 PM, Daniel Stone dan...@fooishbar.org wrote:
indent -linux -bad -bap -blf -bli0 -br -brs -cbi0 -cdw -nce -cs -i4 -hnl
-l80 -lc80 -lp -nbbo -nbc -nbfda -nprs -npcs -npsl -saf -sai -saw -nut
Hi,
On 19 January 2012 06:42, Chase Douglas chase.doug...@canonical.com wrote:
Part of the problem of a coding style is the ongoing maintenance. The
kernel handles this through the check_patch script. This gives rise to
the following questions:
1. Should we just go with linux style, so we
Hi,
On 19 January 2012 10:25, Guillem Jover guil...@hadrons.org wrote:
On Wed, 2012-01-18 at 14:02:01 +1100, Daniel Stone wrote:
So, the commit in my coding-style xserver branch is simply the result of
running this:
indent -linux -bad -bap -blf -bli0 -br -brs -cbi0 -cdw -nce -cs -i4 -hnl
On Thu, Jan 19, 2012 at 03:43:39PM +1100, Daniel Stone wrote:
On 19 January 2012 04:03, Jamey Sharp ja...@minilop.net wrote:
I love this. It invalidates some of my outstanding patches in the best
possible way. But... could you explain (preferably in the commit
message) what evidence you
On Thu, 19 Jan 2012 15:49:06 +1100, Daniel Stone dan...@fooishbar.org wrote:
Actually, non-cuddling else was slightly in the majority -- this was
just based on a quick couple of greps, as was the decision to cuddle
if/for/while statements with their opening greps. For full
disclosure, I
From: Christopher James Halse Rogers christopher.halse.rog...@canonical.com
---
This is prompted by a request from the Ubuntu DX team to conditionally restrict
pointer motion at a screen edge. The Unity launcher appears on a screen edge,
triggered by pointer proximity, and the objective is to
Hello,
I love this. It invalidates some of my outstanding patches in the best
possible way. But... could you explain (preferably in the commit
message) what evidence you have that it hasn't worked? I thought
people were still using XAA.
Indeed, I have just now tested XAA vs EXA on the Lemote
https://bugs.freedesktop.org/show_bug.cgi?id=38491
Michel Dänzer mic...@daenzer.net changed:
What|Removed |Added
AssignedTo|dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=43191
--- Comment #30 from Michal Suchanek hramr...@gmail.com 2012-01-18 05:06:42
PST ---
That's not really much related, that fixes an issue that you might hit when the
tiling is wrong and the gpu locks up.
The current patches at
https://bugs.freedesktop.org/show_bug.cgi?id=41234
--- Comment #7 from j.rehb...@googlemail.com 2012-01-18 13:47:39 PST ---
Is there anyone fixing the bug?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=44916
Bug #: 44916
Summary: Suspend to RAM causes a blank screen with a mouse
cursor on Mobility Radeon HD 2400 XT with radeon
driver.
Classification: Unclassified
Product:
https://bugs.freedesktop.org/show_bug.cgi?id=44916
al...@rambler.ru changed:
What|Removed |Added
CC||al...@rambler.ru
--
Configure
36 matches
Mail list logo
