A freetype font mystery

[Michel Dänzer]

On Tue, 2008-08-19 at 11:41 +0100, Seb James wrote:
> On Tue, 2008-08-19 at 11:11 +0100, Seb James wrote:
> > On Tue, 2008-08-19 at 11:39 +0200, Michel Dänzer wrote:
> > > On Tue, 2008-08-19 at 09:51 +0100, Seb James wrote:
> > > > On Tue, 2008-08-19 at 00:10 +0200, Lukas Hejtmanek wrote:
> > > > > On Mon, Aug 18, 2008 at 10:55:44PM +0100, Seb James wrote:
> > > > > > Having moved my dev system to an Xorg pulled from the git repository,
> > > > > > I'm seeing some odd features in the font rendering and I was hoping
> > > > > > someone could suggest what is up.
> > > > > 
> > > > > what driver are you using? I saw similar symptoms with intel graphics and
> > > > > framebuffercompression enabled.
> > > > 
> > > > I'm using the geode driver.
> > > 
> > > I've pushed a change to xserver Git that might fix (or rather avoid)
> > > this problem.
> > 
> > I'm just trying that now. 
> 
> No joy unfortunately - I see the same behaviour with your changes
> applied.

Yeah, it looks like the geode driver is affected by

        The bug probably still needs to be found and fixed for drivers
        that provide a PrepareComposite hook but can't accelerate text
        rendering though.

So somebody will need to find and fix the bug in exaGlyphs() and friends
when the driver fails to actually accelerate the text rendering
Composite accelerations.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer