1. 15 Apr, 2021 1 commit
  2. 14 Apr, 2021 3 commits
  3. 13 Apr, 2021 1 commit
    • Adam Jackson's avatar
      glx: Lift sending the MakeCurrent request to top-level code · 80b67a3b
      Adam Jackson authored
      Somewhat terrifyingly, we never sent this for direct contexts, which
      means the server never knew the context/drawable bindings. To handle
      this sanely, pull the request code up out of the indirect backend, and
      rewrite the context switch path to call it as appropriate.  This
      attempts to preserve the existing behavior of not calling unbind() on
      the context if its refcount would not drop to zero.
      
      Of course, you can't just do this indiscriminately, because this is GLX
      and extant X servers have bugs and everything is terrible. To wit:
      
      - For 1.20.x prior to 1.20.6, you can bind a direct context once, but
      the second time you try to modify the context's binding you will get
      GLXBadContextTag. This includes unbinding the context. And "deleting"
      the context will leak memory, because it will still appear to be
      current.
      
      - For 1.19 and earlier, glXMakeCurrent(dpy, None, ctx) should be legal
      for GL 3.0+ contexts, but the server will throw BadMatch.
      
      To guard against this, we only send the request for indirect contexts
      unless the server is known good, and only mention one context at a time
      in such a request; if switching between contexts, we first unbind the
      old, and then bind the new. Note that the second VendorRelease() version
      is to catch XFree86 4.x and Xorg [67].x, which almost certainly have the
      above bugs. Other servers might report different version numbers here,
      but we can't do direct rendering against them, so this should be safe.
      
      Fixes: mesa/mesa#4418
      
      Acked-By: Mike Blumenkrantz's avatarMike Blumenkrantz <michael.blumenkrantz@gmail.com>
      Part-of: <mesa/mesa!9992>
      80b67a3b
  4. 05 Apr, 2021 1 commit
  5. 02 Apr, 2021 1 commit
  6. 01 Apr, 2021 2 commits
  7. 31 Mar, 2021 1 commit
  8. 30 Mar, 2021 2 commits
  9. 18 Mar, 2021 1 commit
  10. 17 Mar, 2021 2 commits
  11. 12 Mar, 2021 1 commit
    • Juan A. Suárez's avatar
      ci/broadcom: allow custom kernels · 3f1c3755
      Juan A. Suárez authored
      
      
      So far, testing VC4 and V3D/V3DV requires the CI runners having access
      to a Raspberry Pi 3/4 kernel, and the correspondent modules and
      bootloader files. If a different kernel must be used, it means touching
      the runners to provide them.
      
      This commit adds the option to define an URL pointing to a (compressed)
      tarball containing such files, without requiring dealing with the
      runners. This link is provided through the `BM_BOOTFS` job variable.
      
      The tarball must contain two directories in the root: a `/boot`
      directory (containing the kernel, DTBs and bootloader files), and a
      `/lib/modules` (or `/usr/lib/modules`) with the kernel modules.
      Reviewed-by: Emma Anholt's avatarEric Anholt <eric@anholt.net>
      Signed-off-by: Juan A. Suárez's avatarJuan A. Suarez Romero <jasuarez@igalia.com>
      Part-of: <!9527>
      3f1c3755
  12. 06 Mar, 2021 1 commit
  13. 04 Mar, 2021 1 commit
  14. 24 Feb, 2021 3 commits
  15. 23 Feb, 2021 1 commit
  16. 22 Feb, 2021 2 commits
  17. 19 Feb, 2021 1 commit