1. 10 Aug, 2013 1 commit
  2. 07 Aug, 2013 5 commits
  3. 06 Aug, 2013 9 commits
  4. 29 Jul, 2013 1 commit
  5. 25 Jul, 2013 1 commit
  6. 24 Jul, 2013 7 commits
  7. 23 Jul, 2013 4 commits
  8. 22 Jul, 2013 1 commit
  9. 20 Jul, 2013 1 commit
  10. 19 Jul, 2013 3 commits
  11. 18 Jul, 2013 5 commits
  12. 16 Jul, 2013 1 commit
    • Daniel Vetter's avatar
      tests/prime_nv_api: check multiple foreign imports with flink · 05cc515f
      Daniel Vetter authored
      We want prime to only ever create one native gem object for each
      dma-buf it sees. This can e.g. happen if multiple processes import the
      same foreign dma-buf, e.g. the application imports a yuv frame from
      v4l to encode it into a video stream and the compositor imports it
      into his fd again to display it with an overlay.
      
      Hence add a bunch of tests which check all the various orders in which
      this could happen. Currently they all fail.
      
      Checking flink names is the easiest (and afaik only) way to check
      whether we're indeed dealing with the same object.
      
      This checks both ways, i.e. exporting from i915 and from nouveau, each
      with two variants of the test: One reuses the prime fd, the other
      closes it and creates a new one.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      05cc515f
  13. 15 Jul, 2013 1 commit