[Bug 94574] New: [Intel Skylake] [XV] No picture with mplayer and xv output

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=94574

            Bug ID: 94574
           Summary: [Intel Skylake] [XV] No picture with mplayer and xv
                    output
           Product: xorg
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: jan.burgmeier at unicon-software.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

Created attachment 122349
  --> https://bugs.freedesktop.org/attachment.cgi?id=122349&action=edit
Output of lspci -vv

Hi,

during playback with mplayer and xv output the Xorg log gets spammed with the
following message: "failed to add fb, unable to update video". If drm.debug=6
is actiavted the kernel also outputs: "bad fb modifier 162129721185188224 for
plane 0".

Used software versions:
 - Kernel: 4.4.5
 - Xorg: 1.18.2
 - xf86-video-intel: 2:2.99.917+git20160307
 - libdrm: 2.4.66

I dug a bit deeper and found, that the function sna_video_sprite_show looks
quite equal to get_fb bur without the modifiers handling in the drm struct. I
copied the modifiers pieces aver and video playback started working.

After stopping playback the last frame stays on top and looks like an
'overlay'. It will only close if the surrounding mplayer is closed.

Attached you will find a patch and lspci output.

I'am not familiar with the intel or drm code base so this might or might not be
the correct way of fixing this.

Scaling is also not working with XVideo but as far as I saw this is already a
known issue. If wished I could create a second bug report for it.

Kind regards
Jan Burgmeier

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160316/44bd1a6f/attachment.html>