Bug 859 - Composite/Damage/Fixes integration
Summary: Composite/Damage/Fixes integration
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) All
: high major
Assignee: Stuart Kreitman
QA Contact:
Depends on:
Blocks: 351
  Show dependency treegraph
Reported: 2004-07-12 17:32 UTC by Eric Anholt
Modified: 2004-08-02 02:21 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Eric Anholt 2004-07-12 17:32:56 UTC
It was decided to integrate the Damage, XFixes, and Composite extensions for the
next release.  Damage and XFixes appear to be ready, but we need to write a GC
wrapper to handle the translation to backing pixmaps for Composite so that
binary drivers can continue to work (also, avoids a lot of mess in xaa).  I've
made some steps towards this and have some code to the point of compiling, but I
have my doubts about my handling of GC state changes, and need to wrap some more
Render functions.  Glyph might be the only other Render wrapper that's necessary
for the open-source drivers, but if some other driver (nvidia) were to
accelerate things like triangles or trapezoids it wouldn't be enough.
Comment 1 Eric Anholt 2004-07-15 21:44:20 UTC
Use a slightly more permanent email address, and the one I use in changelogs.
Comment 2 Eric Anholt 2004-07-18 13:16:27 UTC
Apparently Stuart will be handling this.

Eric Anholt wrote:
>So, what is your schedule?  I hadn't heard anything about you guys
>actually actively pushing the Composite bits into X.Org, and I had heard
>that Keith had tried to get the bits from you in the past and failed,
It is my top priority starting this past monday. I have been delayed by 
getting damage-xfixes working in our own x-server
with gnome-magnification and other integrations
Comment 3 Kevin E. Martin 2004-08-02 19:21:50 UTC
Composite, Damage and XFixes have been integrated into the trunk

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.