Summary: | [945G XV texture] Unexpected filtering | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Hugo Jacques <hugo.jacques> | ||||||
Component: | Driver/intel | Assignee: | haihao <haihao.xiang> | ||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | 7.4 (2008.09) | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Hugo Jacques
2009-06-19 10:05:14 UTC
Created attachment 26960 [details]
bitmap used to generate test YV12 pattern
From a thread in the xorg mailing list, it looks like the fix is quite simple. ref: http://lists.freedesktop.org/archives/xorg/2009-June/046155.html Krzysztof Halasa <khc at pm.waw.pl> writes: " > It seems that the fix to i915 is: > > diff --git a/src/i915_video.c b/src/i915_video.c > index 1ef58ac..3b4247c 100644 > --- a/src/i915_video.c > +++ b/src/i915_video.c > @@ -136,8 +136,8 @@ I915DisplayVideoTextured(ScrnInfoPtr pScrn, I830PortPrivPtr pPriv, int id, > format = COLR_BUF_ARGB8888 | DEPTH_FRMT_24_FIXED_8_OTHER; > > OUT_BATCH(LOD_PRECLAMP_OGL | > - DSTORG_HORT_BIAS(0x80) | > - DSTORG_VERT_BIAS(0x80) | > + DSTORG_HORT_BIAS(0x8) | > + DSTORG_VERT_BIAS(0x8) | > format); > > /* front buffer, pitch, offset */ > I think it's safe to commit. Seems like a simple mistake, those fields in that variable seem to be 4-bits wide. Fixes the problem. -- Krzysztof Halasa " Since I am not too versed into the GPU registry manipulation, I will let the bug assignee to verify it. On my system, this seems to be working just fine. Hugo Jacques Pushed, thanks. commit 3418c6c16b108e45f67f3c868d28932266f7a0bc Author: Krzysztof Halasa <khc@pm.waw.pl> Date: Tue Jul 28 10:47:44 2009 +0800 h/v bias in 3DSTATE_DEST_BUFFER_VARIABLES is 4-bits wide Fixes bug #22370 |
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.