1. 25 Sep, 2015 5 commits
  2. 23 Sep, 2015 1 commit
  3. 22 Sep, 2015 3 commits
  4. 21 Sep, 2015 1 commit
    • Aaron Plattner's avatar
      privates: Clear screen-specific keys during CloseScreen · 82eb490b
      Aaron Plattner authored
      The modesetting driver corrupts memory when used after a server regeneration
      because not enough memory is allocated for its pixmap privates.  This happens
      because its call to dixRegisterScreenSpecificPrivateKey() does nothing because
      key->initialized is still TRUE from the first server generation.  However, the
      key is not in the screen's linked list of screen-specific privates because
      that's freed and reallocated during the server generation loop in dix_main().
      
      Fix this by clearing key->initialized before CloseScreen and add a call to
      dixFreeScreenSpecificPrivates() for GPU screens.
      
      v2: Just set key->initialized to FALSE and move dixFreeScreenSpecificPrivates()
      calls to after CloseScreen.
      
      v3: Move dixFreeScreenSpecificPrivates() calls back to just before CloseScreen.
      Signed-off-by: default avatarAaron Plattner <aplattner@nvidia.com>
      Reviewed-by: default avatarKeith Packard <keithp@keithp.com>
      82eb490b
  5. 28 Aug, 2015 1 commit
  6. 24 Aug, 2015 1 commit
    • Olivier Fourdan's avatar
      configurable maximum number of clients · d206c240
      Olivier Fourdan authored
      Make the maximum number of clients user configurable, either from the command
      line or from xorg.conf
      
      This patch works by using the MAXCLIENTS (raised to 512) as the maximum
      allowed number of clients, but allowing the actual limit to be set by the
      user to a lower value (keeping the default of 256).
      
      There is a limit size of 29 bits to be used to store both the client ID and
      the X resources ID, so by reducing the number of clients allowed to connect to
      the X server, the user can increase the number of X resources per client or
      vice-versa.
      
      Parts of this patch are based on a similar patch from Adam Jackson
      <ajax@redhat.com>
      
      This now requires at least xproto 7.0.28
      Signed-off-by: default avatarAdam Jackson <ajax@redhat.com>
      Signed-off-by: default avatarOlivier Fourdan <ofourdan@redhat.com>
      Reviewed-by: default avatarAdam Jackson <ajax@redhat.com>
      Signed-off-by: default avatarKeith Packard <keithp@keithp.com>
      d206c240
  7. 08 Jul, 2015 6 commits
  8. 30 Jun, 2015 1 commit
  9. 20 May, 2015 3 commits
  10. 11 May, 2015 2 commits
  11. 21 Apr, 2015 2 commits
  12. 13 Mar, 2015 1 commit
  13. 11 Feb, 2015 1 commit
    • Alan Coopersmith's avatar
      Get rid of const warnings in XSERVER_INPUT_EVENT dtrace probe calls · 9e002dfc
      Alan Coopersmith authored
      Use typedefs to work around dtrace dropping const qualifiers from probe
      arguments when generating Xserver-dtrace.h.   Add new probes.h header to
      avoid having to replicate these typedefs in every file with dtrace probes.
      
      Gets rid of these warnings from gcc 4.8:
       getevents.c:1096:9:
        warning: passing argument 6 of '__dtrace_Xserver___input__event' discards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1096:9:
        warning: passing argument 7 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1651:9:
        warning: passing argument 6 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1651:9:
        warning: passing argument 7 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1791:9:
        warning: passing argument 6 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1791:9:
        warning: passing argument 7 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1921:9:
        warning: passing argument 6 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
       getevents.c:1921:9:
        warning: passing argument 7 of '__dtrace_Xserver___input__event' disards
        'const' qualifier from pointer target type [enabled by default]
      Signed-off-by: default avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      Reviewed-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      9e002dfc
  14. 04 Jan, 2015 2 commits
  15. 09 Dec, 2014 2 commits
  16. 12 Nov, 2014 4 commits
  17. 29 Oct, 2014 1 commit
    • Keith Packard's avatar
      dix: Untwist transformAbsolute logic, eliminate uninitialized value warnings · 65dd1ba7
      Keith Packard authored
      tranformAbsolute has a pretty simple job, that of running the X/Y
      values from a device through the transformation matrix. The tricky bit
      comes when the current device state doesn't include one of the
      values. In that case, the last delivered value is back-converted to
      device space and used instead.
      
      The logic was twisted though, confusing GCC's uninitialized value
      detection logic and emitting warnings.
      
      This has been fixed by changing the code to:
      
       1) Detect whether the ValuatorMask includes X/Y values
       2) If either are missing, back-convert the current values into ox/oy
       3) When X/Y are present, set ox/oy to the current value
       4) Transform
       5) Store X/Y values if changed or if they were set before.
      Signed-off-by: default avatarKeith Packard <keithp@keithp.com>
      Reviewed-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      65dd1ba7
  18. 27 Oct, 2014 1 commit
  19. 09 Oct, 2014 2 commits