Barton C Massey wrote:
In message 4984a2e2.8060...@xyzw.org you wrote:
I'm going to be avoiding 'git format-patch' for a while
now...
Or at least 'git send-email'. We really prefer
Git-formatted patches, so thanks for doing that. But I, like
you, like to compose my own email.
Several bug fixes, manpage improvements, and addition of new RandR 1.3
options (--current, --{no,}primary).
Julien Cristau (3):
Document the --current option
Document the --primary and --noprimary options
Bump to 1.2.99.4
Keith Packard (4):
Add --current option to use new
On Sun, 2009-02-01 at 14:54 +, Colin Guthrie wrote:
'Twas brillig, and Julien Cristau at 01/02/09 14:17 did gyre and gimble:
Several bug fixes, manpage improvements, and addition of new RandR 1.3
options (--current, --{no,}primary).
Just taken this for a run on 1.6-branch and get this:
On 31 Jan 2009, Michel Dänzer outgrape:
On Fri, 2009-01-30 at 21:59 +, Nix wrote:
On 30 Jan 2009, Michel Dänzer stated:
Trying current xf86-video-ati Git might be good, but my main suggestion
would be to try xserver Git server-1.6-branch with EXA.
OK. Do I need to upgrade Mesa or
On Sunday 01 February 2009 05:45:04 Jin, Gordon wrote:
Btw, with EXA and kernel = 2.6.28 I can't get 3D working. glxinfo
says that I'm using direct rendering, but ~9fps in quake3 is not
hardware accelerated 3D, is it?
Maybe you could file a bug with glxinfo output attached.
Done, it's bug
Le dimanche 01 février 2009 à 12:54 +, Nix a écrit :
On 31 Jan 2009, Michel Dänzer outgrape:
I think a big part of the motivation for client side fonts was indeed
anti-aliasing, so if you don't want AA and core fonts are faster for
you, just use core fonts?
That's Not really
'Twas brillig, and Julien Cristau at 01/02/09 14:17 did gyre and gimble:
Several bug fixes, manpage improvements, and addition of new RandR 1.3
options (--current, --{no,}primary).
Just taken this for a run on 1.6-branch and get this:
X Error of failed request: BadLength (poly request too
'Twas brillig, and Julien Cristau at 01/02/09 15:03 did gyre and gimble:
On Sun, 2009-02-01 at 14:54 +, Colin Guthrie wrote:
'Twas brillig, and Julien Cristau at 01/02/09 14:17 did gyre and gimble:
Several bug fixes, manpage improvements, and addition of new RandR 1.3
options (--current,
On Sat, 2009-01-31 at 02:30 +, John Tapsell wrote:
2009/1/31 Bryce Harrington br...@canonical.com:
On Fri, Jan 30, 2009 at 01:29:49PM -0800, Eric Anholt wrote:
$ glxgears
Failed to initialize TTM buffer manager. Falling back to classic.
300 frames in 5.0 seconds = 59.884 FPS
On Fri, 2009-01-30 at 18:11 -0800, Bryce Harrington wrote:
On Fri, Jan 30, 2009 at 01:29:49PM -0800, Eric Anholt wrote:
$ glxgears
Failed to initialize TTM buffer manager. Falling back to classic.
300 frames in 5.0 seconds = 59.884 FPS
299 frames in 5.0 seconds = 59.621 FPS
300
Hi,
I just tried to compile xorg/git with the xorg-git.sh shell script,
and it fails in xf86-input-keyboard with the following error:
kbd.c: In function 'KbdProc':
kbd.c:567: warning: passing argument 1 of 'InitKeyboardDeviceStruct'
from incompatible pointer type
kbd.c:567: warning: passing
Hi Clemens,
Hi, I just tried to compile xorg/git with the xorg-git.sh shell
script, and it fails in xf86-input-keyboard with the following
error:
xf86-input-keyboard has been broken for more than a week now. Worse,
the server segfaults on launch. Input folks, is someone working on
On 1 Feb 2009, Nicolas Mailhot uttered the following:
From a distribution point of view, apps which use fontconfig almost
never present problems (because fontconfig will do all kinds of smart
stuff like substituting missing fonts transparently), while apps that
use core fonts have a long
Hi Chris,
xf86-input-keyboard has been broken for more than a week now. Worse,
the server segfaults on launch. Input folks, is someone working on
landing fixes for this breakage?
Yes, I experience the same - but I thought this was caused by the
missing keyboard stuff.
Thanks your reply,
Finally, we decided to go for a 1.0 release since 0.99.3 has been slumbering
for too long.
Notable improvements since the 0.15.2 release:
- Improved device autoscaling. The device now reads the kernel's event
interface and adjusts most parameters based on the information received.
This gives
In Xinerama all windows hang off the first root window. Crossing the screens
must not reset the spriteTrace, otherwise picking fails and events are sent to
the root window.
X.Org Bug 18668 http://bugs.freedesktop.org/show_bug.cgi?id=18668
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
On Sun, Jan 25, 2009 at 2:48 PM, Ben Gamari bgam...@gmail.com wrote:
Strangely enough, before I login (in gdm) things seem to behave as
they should. Directly after I login though (even before my own minimal
~/.Xmodmap has been loaded), the behavior I described earlier begins.
- Ben
It's
On Sun, Feb 01, 2009 at 05:44:00PM -0500, Chris Ball wrote:
Hi Clemens,
Hi, I just tried to compile xorg/git with the xorg-git.sh shell
script, and it fails in xf86-input-keyboard with the following
error:
xf86-input-keyboard has been broken for more than a week now. Worse,
While trying to fix some of the warnings that gcc generates when
compiling the xserver, I came across two which appear to be real bugs.
Since they don't appear to be trivial to fix, I'm posting them here for
further review:
Xi/setbmap.c:110 in ProcXSetDeviceButtonMapping()
Alan Coopersmith (1):
Add README with pointers to mailing list, bugzilla git repos
Peter Hutterer (4):
Don't print xkb options twice to the log file.
Reshuffle property initialization.
Protect against zero-sized property values. #19882
evdev 2.1.2
git tag:
On 02/02/2009 02:35 AM, Tomas Carnecky wrote:
While trying to fix some of the warnings that gcc generates when
compiling the xserver, I came across two which appear to be real bugs.
Since they don't appear to be trivial to fix, I'm posting them here for
further review:
Xi/setbmap.c:110 in
On Mon, Feb 02, 2009 at 03:00:52AM +0100, Tomas Carnecky wrote:
On 02/02/2009 02:35 AM, Tomas Carnecky wrote:
While trying to fix some of the warnings that gcc generates when
compiling the xserver, I came across two which appear to be real bugs.
Since they don't appear to be trivial to fix,
2009/2/1 Ian Romanick i...@freedesktop.org:
On Sat, 2009-01-31 at 02:30 +, John Tapsell wrote:
2009/1/31 Bryce Harrington br...@canonical.com:
On Fri, Jan 30, 2009 at 01:29:49PM -0800, Eric Anholt wrote:
$ glxgears
Failed to initialize TTM buffer manager. Falling back to classic.
Hi,
I'm seeing this tonight after updating from git (around 23:00 EST).
.
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
Oops, forgot to mention I'm running the 2.6.28 Intel kernel from
http://intellinuxgraphics.org/2008Q4.html.
--- On Sun, 2/1/09, Joe Smith stop...@yahoo.com wrote:
From: Joe Smith stop...@yahoo.com
Subject: fatal error in latest intel, drm, mesa, xserver 1.6
To: xorg@lists.freedesktop.org
I've seen a similar problem with DRI2. Is there a related fix for this?
Thanks!
# glxinfo
name of display: :0.0
X Error of failed request: BadLength (poly request too large or internal Xlib
length error)
Major opcode of failed request: 135 (DRI2)
Minor opcode of failed request: 1 ()
On Sun, Feb 01, 2009 at 11:55:56AM -0800, Ian Romanick wrote:
On Fri, 2009-01-30 at 18:11 -0800, Bryce Harrington wrote:
On Fri, Jan 30, 2009 at 01:29:49PM -0800, Eric Anholt wrote:
$ glxgears
Failed to initialize TTM buffer manager. Falling back to classic.
300 frames in 5.0
27 matches
Mail list logo
