Travis, if it works for nvidia and ati's proprietary drivers, then how is this a limitation of the X-Server? Wouldn't it just be a limitation of specific drivers? and even if it's a limitation of X that they worked around, it means that a work-around is possible.
Just to add to the discussion, since there is no specific information here, is this link:
Supposedly this will be solved with DRI2, but I don't know when that is planned by the X.org folks. Which also comes back to the question of how the nvidia / ati (fglrx) drivers work yet other don't if this really is just a limitation of DRI.
Travis, if it works for nvidia and ati's proprietary drivers, then how is this a limitation of the X-Server? Wouldn't it just be a limitation of specific drivers? and even if it's a limitation of X that they worked around, it means that a work-around is possible.
Just to add to the discussion, since there is no specific information here, is this link:
http:// forum.compiz- fusion. org/showthread. php?t=6944
Supposedly this will be solved with DRI2, but I don't know when that is planned by the X.org folks. Which also comes back to the question of how the nvidia / ati (fglrx) drivers work yet other don't if this really is just a limitation of DRI.