Bug 9077 - resort to power-of-two textures if needed
Summary: resort to power-of-two textures if needed
Alias: None
Product: xorg
Classification: Unclassified
Component: App/compiz (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: David Reveman
QA Contact: Xorg Project Team
Depends on:
Reported: 2006-11-18 13:36 UTC by Tormod Volden
Modified: 2007-09-05 16:26 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Description Tormod Volden 2006-11-18 13:36:02 UTC
(from https://launchpad.net/bugs/72365)
The S3 Savage video hardware does not support "non power of two textures" and
compiz therefore fails to start. Compiz should have the ability to use only POT
Comment 1 David Reveman 2006-11-20 14:58:32 UTC
Assuming that textures are the same size as the pixmaps being bound to them
makes things a lot more convenient and removes tricky special cases that plugins
would have to be aware of.

GLX_EXT_tfp requires npot textures so if they are not available compiz would
have to MakeCurrent-CopyTexSubImage the pixmap content, which is slower and
requires more video memory. Most hardware that doesn't support npot textures is
already low on video memory so even if compiz would resort to pot textures if
needed it might not be usable anyhow.
Comment 2 Tormod Volden 2006-11-20 15:44:01 UTC
Sniff, no compiz for me? https://bugs.freedesktop.org/show_bug.cgi?id=8758#c1
Yes, I have only up to 32 MB of video memory. But shouldn't there be some
fallback, like compiz starting but with reduced bling?
Comment 3 Singpolyma 2007-02-06 14:30:24 UTC
This error occurs with more than just the Savage card...  if some plugins (ie 'reduced bling) didn't work on POT that would be fine... but having it fail completely in annoying...
Comment 4 Daniel Stone 2007-02-27 01:34:44 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

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.