| Summary: | RenderComposite with XAA renders at wrong position if vertically scaled. | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Kusanagi Kouichi <slash> | ||||||||||||||
| Component: | Server/Acceleration/XAA | Assignee: | Søren Sandmann Pedersen <soren.sandmann> | ||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||
| Severity: | critical | ||||||||||||||||
| Priority: | medium | CC: | grfgguvf+xorgbz, tjaalton, xake | ||||||||||||||
| Version: | unspecified | ||||||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Kusanagi Kouichi
2007-12-23 05:10:32 UTC
Created attachment 13321 [details]
xorg.conf
Created attachment 13322 [details]
Xorg.0.log
Created attachment 13323 [details]
testcase
This should fill entire window with white.
Created attachment 13324 [details]
Not scaled. 320 pixel height.
Created attachment 13325 [details]
Change height to 280 pixel.
Created attachment 13326 [details]
Change height to 360 pixel.
*** Bug 14210 has been marked as a duplicate of this bug. *** If I disabled offscreen pixmap, the problem disappears. The issue here is almost certainly that FbComposite offsets the composite operation by the coordinates of the drawable with no regard to the transformation. Fixing probably involves making image_from_pict() do the conversion, and somehow fixing up miSourceValidate Moving to 7.5 tracker. Hacked around in server-1.5-branch, see further discussion on bug #15098 for motivation and workaround doc. dropping from the release tracker: xaa is deprecated, offscreen pixmaps are not enabled by default, and this _may_ be fixed already. I believe this is fixed. |
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.