Re: Solved! (was Re: client-side font rendering very very slow in X.org xserver 1.5.3 w/r200: massive fetches from VRAM, why?)

2009-02-05 Thread Michel Dänzer
On Thu, 2009-02-05 at 00:29 +, Nix wrote: augh! blasted --disable-builtin-fonts, why isn't it the default? It's gone in Git master, the builtins are always available as a fallback for the real FontPath now. There's discussion about merging this nice solution for 1.6. but the most

Re: Solved! (was Re: client-side font rendering very very slow in X.org xserver 1.5.3 w/r200: massive fetches from VRAM, why?)

2009-02-05 Thread Colin Guthrie
'Twas brillig, and Michel Dänzer at 05/02/09 08:15 did gyre and gimble: On Thu, 2009-02-05 at 00:29 +, Nix wrote: augh! blasted --disable-builtin-fonts, why isn't it the default? It's gone in Git master, the builtins are always available as a fallback for the real FontPath now. There's

Solved! (was Re: client-side font rendering very very slow in X.org xserver 1.5.3 w/r200: massive fetches from VRAM, why?)

2009-02-04 Thread Nix
On 3 Feb 2009, Dan Nicholson uttered the following: The output isn't quite what I'd expect, but I think this is because it's using the builtin fonts only. Try rebuilding the server with --disable-builtin-fonts, or apply this patch that's a candidate for augh! blasted --disable-builtin-fonts,