1. 15 Aug, 2019 5 commits
    • Olivier Fourdan's avatar
      meson: Build miext/sync for Xwayland · e8a85ba8
      Olivier Fourdan authored
      
      
      When using the Meson build system, miext/sync would be build only for
      dri3.
      
      As a result, when building with Meson without DRI3 enabled, Xwayland
      would fail to link because `miSyncShmScreenInit()` is nowhere to be
      found.
      
      Make sure to build miext/sync for either DRI3 or Xwayland.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      e8a85ba8
    • Olivier Fourdan's avatar
      meson: Move requirements in a single place · c0bbc29a
      Olivier Fourdan authored
      
      
      Some modules are required in multiple places in the meson file.
      
      Move the actual requirements to the top of the file as a variable so
      that updating a version does not require changing the actual value in
      multiple places.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      c0bbc29a
    • Olivier Fourdan's avatar
      configure/xwayland: No libdrm nor epoxy without glamor · bf758660
      Olivier Fourdan authored
      
      
      When building Xwayland without neither DRI nor GLamor support enabled
      with the autotools build system, the resulting binary would still link
      against libdrm and epoxy even though those are not used/needed.
      
      Make sure we require and link against libdrm and epoxy only if needed.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      bf758660
    • Adam Jackson's avatar
      composite: Be more paranoid in compDestroyDamage · 5096fcd4
      Adam Jackson authored
      Consider these two facts:
      
      - You can't rely on resource deletion order
      - damageDestroyWindow automatically destroys any damage listener
        connected to the doomed window
      
      Now consider a redirected window being destroyed. If the damage
      associated with the redirection is destroyed before the window, then
      when compFreeClientWindow tries to unredirect the window, the call to
      compSetParentPixmap may see that cw->damageRegistered is still true, and
      call DamageUnregister(NULL) (because compDestroyDamage already zeroed
      out cw->damage), and you get a backtrace that looks like:
      
          #6  <signal handler called>
          #7  DamageUnregister (pDamage=0x0) at damage.c:1773   <-----------------
          #8  0x000000000051f767 in compSetParentPixmap (pWin=pWin@entry=0x28489c0) at compalloc.c:646
          #9  0x000000000051fa01 in compFreeClientWindow (pWin=0x28489c0, id=<optimized out>) at compalloc.c:291
          #10 0x000000000051a499 in FreeCompositeClientWindow (value=<optimized out>, ccw...
      5096fcd4
    • Adam Jackson's avatar
      global: Remove BUILD_DATE and BUILD_TIME · 3c78d637
      Adam Jackson authored
      All this does is make reproducible builds impossible.
      3c78d637
  2. 10 Aug, 2019 1 commit
    • Matt Turner's avatar
      dix: Assert noPanoramiXExtension is false in PanoramiX code · 61aa40ae
      Matt Turner authored
      When compiling with link time optimization, GCC thinks it's discovered
      undefined behavior:
      
      events.c: In function 'XineramaConfineCursorToWindow':
      events.c:609:13: warning: iteration 2147483647 invokes undefined behavior [-Waggressive-loop-optimizations]
      events.c:609:11: note: within this loop
      events.c:605:49: warning: array subscript -1 is below array bounds of 'struct _Window *[16]' [-Warray-bounds]
      events.c:606:31: warning: array subscript -1 is below array bounds of 'struct _Screen *[16]' [-Warray-bounds]
      events.c:610:39: warning: array subscript -2 is below array bounds of 'struct _Screen *[16]' [-Warray-bounds]
      events.c:617:38: warning: array subscript -2 is below array bounds of 'struct _Window *[16]' [-Warray-bounds]
      events.c:619:35: warning: array subscript -2 is below array bounds of 'struct _Screen *[16]' [-Warray-bounds]
      
      This results from
      
          i = PanoramiXNumScreens - 1;
      
          RegionCopy(&pSprite->Reg1, &pSprite->windows[i]->borderSize);
          off_x = screenInfo.screens[i]->x;
          off_y = screenInfo.screens[i]->y;
      
      where GCC believes that PanoramiXNumScreens might be 0. Unfortunately
      GCC is just smart enough to be an annoyance because this case is not
      actually possible: XineramaConfineCursorToWindow() is only called when
      noPanoramiXExtension is false, and if noPanoramiXExtension is false then
      PanoramiXNumScreens must be >1 (see PanoramiXExtensionInit()).
      
      So, add an assert(!noPanoramiXExtension), which to my surprise provides
      GCC with information even in release builds and lets GCC understand that
      the code is not doing anything that is undefined behavior.
      
      I chose this solution instead of the proposed assert(i >= 0) because the
      same pattern occurs in CheckVirtualMotion() but is inside an
      'if (!noPanoramiXExtension)' and does not generate any warnings.
      
      Fixes: xorg/xserver#590
      
      Signed-off-by: Matt Turner's avatarMatt Turner <mattst88@gmail.com>
      61aa40ae
  3. 09 Aug, 2019 3 commits
  4. 07 Aug, 2019 1 commit
    • Dave Airlie's avatar
      xf86: autobind GPUs to the screen · 078277e4
      Dave Airlie authored
      
      
      This is a modified version of a patch we've been carry-ing in Fedora and
      RHEL for years now. This patch automatically adds secondary GPUs to the
      master as output sink / offload source making e.g. the use of
      slave-outputs just work, with requiring the user to manually run
      "xrandr --setprovideroutputsource" before he can hookup an external
      monitor to his hybrid graphics laptop.
      
      There is one problem with this patch, which is why it was not upstreamed
      before. What to do when a secondary GPU gets detected really is a policy
      decission (e.g. one may want to autobind PCI GPUs but not USB ones) and
      as such should be under control of the Desktop Environment.
      
      Unconditionally adding autobinding support to the xserver will result
      in races between the DE dealing with the hotplug of a secondary GPU
      and the server itself dealing with it.
      
      However we've waited for years for any Desktop Environments to actually
      start doing some sort of autoconfiguration of secondary GPUs and there
      is still not a single DE dealing with this, so I believe that it is
      time to upstream this now.
      
      To avoid potential future problems if any DEs get support for doing
      secondary GPU configuration themselves, the new autobind functionality
      is made optional. Since no DEs currently support doing this themselves it
      is enabled by default. When DEs grow support for doing this themselves
      they can disable the servers autobinding through the servers cmdline or a
      xorg.conf snippet.
      Signed-off-by: Dave Airlie's avatarDave Airlie <airlied@gmail.com>
      [hdegoede@redhat.com: Make configurable, fix with nvidia, submit upstream]
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Reviewed-by: Emma Anholt's avatarEric Anholt <eric@anholt.net>
      Reviewed-by: Emil Velikov's avatarEmil Velikov <emil.velikov@collabora.com>
      ---
      Changes in v2:
      -Make the default enabled instead of installing a xorg.conf
       snippet which enables it unconditionally
      
      Changes in v3:
      -Handle GPUScreen autoconfig in randr/rrprovider.c, looking at
       rrScrPriv->provider, rather then in hw/xfree86/modes/xf86Crtc.c
       looking at xf86CrtcConfig->provider. This fixes the autoconfig not
       working with the nvidia binary driver
      078277e4
  5. 06 Aug, 2019 5 commits
  6. 05 Aug, 2019 1 commit
    • Ross Burton's avatar
      sdksyms.sh: don't embed the build path · 6f41bf31
      Ross Burton authored
      This script generates a header that has a comment containing the build path for
      no real reason.  As this source can end up deployed on targets in debug packages
      this means there is both potentially sensitive information leakage about the
      build environment, and a source of change for reproducible builds.
      6f41bf31
  7. 04 Aug, 2019 1 commit
  8. 31 Jul, 2019 2 commits
    • Olivier Fourdan's avatar
      xwayland: Fix build warning without glamor · f107bde1
      Olivier Fourdan authored
      
      
      Building Xwayland without glamor support would raise a warning at build
      time:
      
        xwayland.c: In function ‘xwl_screen_init’:
        xwayland.c:980:10: warning: unused variable ‘use_eglstreams’
          980 |     Bool use_eglstreams = FALSE;
              |          ^~~~~~~~~~~~~~
      
      When building without glamor support, we cannot have EGL Streams support
      either, the two being related. So we do not need to declare the variable
      `use_eglstreams` if glamor is not enabled.
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      Reviewed-by: Michel Dänzer's avatarMichel Dänzer <michel.daenzer@amd.com>
      f107bde1
    • Olivier Fourdan's avatar
      xwayland: Fix build without glamor · 8587bbd8
      Olivier Fourdan authored
      When building Xwayland without glamor support enabled using automake,
      the build would fail at link time trying to find `glamor_block_handler`:
      
        /usr/bin/ld: xwayland-glx.o: in function `egl_drawable_wait_x':
        hw/xwayland/xwayland-glx.c:102: undefined reference to
        `glamor_block_handler'
      
      Make sure we don't try to build `xwayland-glx.c` without glamor in the
      Xwayland Makefile.
      
      Note: Meson build is fine because it's already build only with glamor
      enabled.
      
      Fixes: commit 84692415
      
       - "xwayland: Add EGL-backed GLX provider"
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      8587bbd8
  9. 23 Jul, 2019 4 commits
  10. 22 Jul, 2019 1 commit
  11. 21 Jul, 2019 6 commits
  12. 17 Jul, 2019 3 commits
  13. 16 Jul, 2019 1 commit
  14. 15 Jul, 2019 1 commit
  15. 12 Jul, 2019 1 commit
  16. 10 Jul, 2019 2 commits
  17. 03 Jul, 2019 1 commit
  18. 01 Jul, 2019 1 commit
    • Samuel Thibault's avatar
      Fix crash on XkbSetMap · fabc4219
      Samuel Thibault authored
      Since group_info and width are used for the key actions allocations,
      when modifying them we need to take care of reallocation key actions if
      needed.
      fabc4219