All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73200] New: vdpau-GL interop fails due to different screen objects
Date: Wed, 01 Jan 2014 05:41:46 +0000	[thread overview]
Message-ID: <bug-73200-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2070 bytes --]

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

          Priority: medium
            Bug ID: 73200
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: vdpau-GL interop fails due to different screen objects
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: ystreet00-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: 10.0
         Component: Drivers/DRI/nouveau
           Product: Mesa

Basically I'm trying out the GL_NV_vdpau_interop extension and it's failing
with GL_INVALID_OPERATION inside mesa/state_tracker/st_vdpau.c:121
st_vdpau_map_surface() because the GL screen and the vdpau screen are
different.

Things I've tried:
 - Straight vdpau/x11 (no GL) - works nicely
 - #if 0 the screen equal check - Fails with 'Kernel rejected pushbuf'.  From
this I made the assumption that the screen represents some gpu context and thus
the object space that is addressable.  Also what I gathered from the libdrm
code.
 - Copying the fd hash table from the radeon_drm_winsys_create() into
nouveau_drm_screen_create().  That fails to work because vl_screen_create() and
dri2CreateScreen() both create seperate drm fds resulting in different entries
in the hash table (that's not the same - see next point)
 - static screen singleton (ignoring subsequent drm fds) however
nouveau_drm_screen_create is duplicated in both
/usr/lib/vdpau/libvdpau_nouveau.so and /usr/lib/xorg/modules/dri/nouveau_dri.so
and thus have different locations.

So all of my attempts to get the screens the same have so far failed and I am
not all that familiar with mesa internals to suggest a solution :)

Versions:
$ uname -a
Linux matt-arch 3.12.6-1-ARCH #1 SMP PREEMPT Fri Dec 20 19:39:00 CET 2013
x86_64 GNU/Linux
$ pacman -Si mesa | grep Version
Version        : 10.0.1-1
$ pacman -Si libdrm | grep Version
Version        : 2.4.50-1

Some logs follow.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3322 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-01-01  5:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01  5:41 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-73200-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-01  5:43   ` [Bug 73200] vdpau-GL interop fails due to different screen objects bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-01  6:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-01  6:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-25  3:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 10:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 11:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 16:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-06 20:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  5:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  5:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08  9:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-08 22:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-11 10:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-11 11:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-11 12:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-73200-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.