Summary: | The video with Xv acceleration covers window on top it under extended output mode | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Michael Chang <mchang> | ||||||
Component: | Driver/intel | Assignee: | Chris Wilson <chris> | ||||||
Status: | CLOSED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | unspecified | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Michael Chang
2011-03-15 21:10:45 UTC
Created attachment 44491 [details]
Xv video covers active foreground window
Created attachment 44499 [details]
Screenshot of mplayer with "-vo xv" option
To eliminate the possible influence of GStreamer framework, use mplayer to test again and still get a failed result.
I can't reproduce with the latest driver: Libdrm: (master)2.4.24-6-g3b04c73650b5e9bbcb602fdb8cea0b16ad82d0c0 Mesa: (7.10)d59da648178f04f68232ee8a8994843c6b547af8 Xserver: xorg-server-1.10.0 Xf86_video_intel:(master)2.14.901-3-g014fc7abb7b2cc2110e3ab9a0bd6f7cff2c64c05 Kernel: (drm-intel-fixes) 91355834646328e7edc6bd25176ae44bcd7386c7 commit ee740778f5d5355c04f6fc4564f598993b106d62 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Mar 16 08:37:24 2011 +0000 i915/video: Clip indirect Xv output In the case of a singular clip box and rendering onto the front buffer larger than 2048, the clip extents were being ignored. Here we can simply reduce the size of the indirect pixmap to the clip extents. Reported-by: Michael Chang <mchang@novell.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=35346 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Chris, I git-pulled to contain this fixing commit. Verified fixing of this issue on my side. Thereafter, I'd like to change the status to closed. Many thanks for your quick respond and fixing. :) |
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.