1. 19 May, 2010 1 commit
  2. 14 May, 2010 3 commits
  3. 13 May, 2010 1 commit
    • Jamey Sharp's avatar
      Kill DoChangeGC in favor of dixChangeGC. · 65cedf39
      Jamey Sharp authored
      This doesn't change any behavior, but it isn't clear whether NullClient
      is correct in all cases. As ajax says,
      
      > For most of these changes, I think it's correct to use NullClient,
      > since they are server-initiated changes and should not fail for (eg)
      > xace reasons. ... At any rate, you're certainly not changing any
      > semantics by leaving them all as NullClient, so this patch can't be
      > more wrong than before.
      Signed-off-by: Jamey Sharp's avatarJamey Sharp <jamey@minilop.net>
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      65cedf39
  4. 12 May, 2010 1 commit
  5. 02 May, 2010 1 commit
  6. 28 Sep, 2009 1 commit
  7. 29 May, 2009 1 commit
    • Jeremy Huddleston's avatar
      XQuartz: Fix alpha to be 1 (screenshots bug, etc) · f2151f1b
      Jeremy Huddleston authored
      This is related to: bc964ff1
      XQuartz: Stab at fixing the alpha 0/1 bug (screenshots, etc) by pulling in some old code that got gutted from rootless.
      
      which was on the 1.4 branch and implemented in fbPaintWindow.  Now that fbPaintWindow is gone, this is now in miPaintWindow().
      (cherry picked from commit 032173f6)
      f2151f1b
  8. 29 Apr, 2009 1 commit
  9. 16 Feb, 2009 1 commit
  10. 07 Feb, 2009 1 commit
  11. 22 Jan, 2009 1 commit
  12. 12 Dec, 2008 1 commit
    • Peter Hutterer's avatar
      Remove #define NEED_EVENTS and NEED_REPLIES · cb95642d
      Peter Hutterer authored
      A grep on xorg/* revealed there's no consumer of this define.
      
      Quote Alan Coopersmith:
      "The consumer was in past versions of the headers now located
      in proto/x11proto - for instance, in X11R6.0's xc/include/Xproto.h,
      all the event definitions were only available if NEED_EVENTS were
      defined, and all the reply definitions required NEED_REPLIES.
      
      Looks like Xproto.h dropped them by X11R6.3, which didn't have
      the #ifdef's anymore, so these are truly ancient now."
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@redhat.com>
      Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      cb95642d
  13. 03 Dec, 2008 1 commit
    • Paulo Cesar Pereira de Andrade's avatar
      Rework symbol visibility for easier maintenance · 49f77fff
      Paulo Cesar Pereira de Andrade authored
        Save in a few special cases, _X_EXPORT should not be used in C source
      files. Instead, it should be used in headers, and the proper C source
      include that header. Some special cases are symbols that need to be
      shared between modules, but not expected to be used by external drivers,
      and symbols that are accessible via LoaderSymbol/dlopen.
      
        This patch also adds conditionally some new sdk header files, depending
      on extensions enabled. These files were added to match pattern for
      other extensions/modules, that is, have the headers "deciding" symbol
      visibility in the sdk. These headers are:
      o Xext/panoramiXsrv.h, Xext/panoramiX.h
      o fbpict.h (unconditionally)
      o vidmodeproc.h
      o mioverlay.h (unconditionally, used only by xaa)
      o xfixes.h (unconditionally, symbols required by dri2)
      
        LoaderSymbol and similar functions now don't have different prototypes,
      in loaderProcs.h and xf86Module.h, so that both headers can be included,
      without the need of defining IN_LOADER.
      
        xf86NewInputDevice() device prototype readded to xf86Xinput.h, but
      not exported (and with a comment about it).
      49f77fff
  14. 30 Nov, 2008 1 commit
    • Paulo Cesar Pereira de Andrade's avatar
      Export symbols defined in the sdk. · d6cbd451
      Paulo Cesar Pereira de Andrade authored
        This is the biggest "visibility" patch. Instead of doing a "export"
      symbol on demand, export everything in the sdk, so that if some module
      fails due to an unresolved symbol, it is because it is using a symbol
      not in the sdk.
      
        Most exported symbols shouldn't really be made visible, neither
      advertised in the sdk, as they are only used by a single shared object.
      
        Symbols in the sdk (or referenced in sdk macros), but not defined
      anywhere include:
      XkbBuildCoreState()
      XkbInitialMap
      XkbXIUnsupported
      XkbCheckActionVMods()
      XkbSendCompatNotify()
      XkbDDXFakePointerButton()
      XkbDDXApplyConfig()
      _XkbStrCaseCmp()
      _XkbErrMessages[]
      _XkbErrCode
      _XkbErrLocation
      _XkbErrData
      XkbAccessXDetailText()
      XkbNKNDetailMaskText()
      XkbLookupGroupAndLevel()
      XkbInitAtoms()
      XkbGetOrderedDrawables()
      XkbFreeOrderedDrawables()
      XkbConvertXkbComponents()
      XkbWriteXKBSemantics()
      XkbWriteXKBLayout()
      XkbWriteXKBKeymap()
      XkbWriteXKBFile()
      XkbWriteCFile()
      XkbWriteXKMFile()
      XkbWriteToServer()
      XkbMergeFile()
      XkmFindTOCEntry()
      XkmReadFileSection()
      XkmReadFileSectionName()
      InitExtInput()
      xf86CheckButton()
      xf86SwitchCoreDevice()
      RamDacSetGamma()
      RamDacRestoreDACValues()
      xf86Bpp
      xf86ConfigPix24
      xf86MouseCflags[]
      xf86SupportedMouseTypes[]
      xf86NumMouseTypes
      xf86ChangeBusIndex()
      xf86EntityEnter()
      xf86EntityLeave()
      xf86WrapperInit()
      xf86RingBell()
      xf86findOptionBoolean()
      xf86debugListOptions()
      LoadSubModuleLocal()
      LoaderSymbolLocal()
      getInt10Rec()
      xf86CurrentScreen
      xf86ReallocatePciResources()
      xf86NewSerialNumber()
      xf86RandRSetInitialMode()
      fbCompositeSolidMask_nx1xn
      fbCompositeSolidMask_nx8888x0565C
      fbCompositeSolidMask_nx8888x8888C
      fbCompositeSolidMask_nx8x0565
      fbCompositeSolidMask_nx8x0888
      fbCompositeSolidMask_nx8x8888
      fbCompositeSrc_0565x0565
      fbCompositeSrc_8888x0565
      fbCompositeSrc_8888x0888
      fbCompositeSrc_8888x8888
      fbCompositeSrcAdd_1000x1000
      fbCompositeSrcAdd_8000x8000
      fbCompositeSrcAdd_8888x8888
      fbGeneration
      fbIn
      fbOver
      fbOver24
      fbOverlayGeneration
      fbRasterizeEdges
      fbRestoreAreas
      fbSaveAreas
      composeFunctions
      VBEBuildVbeModeList()
      VBECalcVbeModeIndex()
      TIramdac3030CalculateMNPForClock()
      shadowBufPtr
      shadowFindBuf()
      miRRGetScreenInfo()
      RRSetScreenConfig()
      RRModePruneUnused()
      PixmanImageFromPicture()
      extern int miPointerGetMotionEvents()
      miClipPicture()
      miRasterizeTriangle()
      fbPush1toN()
      fbInitializeBackingStore()
      ddxBeforeReset()
      SetupSprite()
      InitSprite()
      DGADeliverEvent()
      
        SPECIAL CASES
      o defined as _X_INTERNAL
      	xf86NewInputDevice()
      o defined as static
      	fbGCPrivateKey
      	fbOverlayScreenPrivateKey
      	fbScreenPrivateKey
      	fbWinPrivateKey
      o defined in libXfont.so, but declared in xorg/dixfont.h
      	GetGlyphs()
      	QueryGlyphExtents()
      	QueryTextExtents()
      	ParseGlyphCachingMode()
      	InitGlyphCaching()
      	SetGlyphCachingMode()
      d6cbd451
  15. 03 Oct, 2008 1 commit
  16. 18 Aug, 2008 1 commit
  17. 24 Jul, 2008 1 commit
  18. 28 May, 2008 1 commit
  19. 01 Mar, 2008 1 commit
  20. 18 Jan, 2008 1 commit
  21. 05 Nov, 2007 1 commit
  22. 13 Sep, 2007 1 commit
    • Eric Anholt's avatar
      Remove the PaintWindow optimization. · e4d11e58
      Eric Anholt authored
      This was an attempt to avoid scratch gc creation and validation for paintwin
      because that was expensive.  This is not the case in current servers, and the
      danger of failure to implement it correctly (as seen in all previous
      implementations) is high enough to justify removing it.  No performance
      difference detected with x11perf -create -move -resize -circulate on Xvfb.
      Leave the screen hooks for PaintWindow* in for now to avoid ABI change.
      e4d11e58
  23. 12 Sep, 2007 3 commits
  24. 25 Aug, 2007 1 commit
    • Adam Jackson's avatar
      Implement core protocol backing store exclusively in terms of Composite. · ae7f71a8
      Adam Jackson authored
      Composite's automatic redirection is a more general mechanism than the
      ad-hoc BS machinery, so it's much prettier to implement the one in terms
      of the other.  Composite now wraps ChangeWindowAttributes and activates
      automatic redirection for windows with backing store requested.  The old
      backing store infrastructure is completely gutted: ABI-visible structures
      retain the function pointers, but they never get called, and all the
      open-coded conditionals throughout the DIX layer to implement BS are gone.
      
      Note that this is still not a strictly complete implementation of backing
      store, since Composite will throw the bits away on unmap and therefore
      WhenMapped and Always hints are equivalent.
      ae7f71a8
  25. 14 Aug, 2007 1 commit
  26. 09 Mar, 2007 1 commit
  27. 21 Jul, 2006 1 commit
  28. 15 Feb, 2006 1 commit
  29. 03 Jul, 2005 2 commits
  30. 01 Jul, 2005 1 commit
  31. 20 Apr, 2005 1 commit
    • Daniel Stone's avatar
      Fix includes right throughout the Xserver tree: · 292c4cff
      Daniel Stone authored
      change "foo.h" to <X11/foo.h> for core headers, e.g. X.h, Xpoll.h;
      change "foo.h", "extensions/foo.h" and "X11/foo.h" to
          <X11/extensions/foo.h> for extension headers, e.g. Xv.h;
      change "foo.[ch]" to <X11/Xtrans/foo.[ch]> for Xtrans files.
      292c4cff
  32. 04 May, 2004 1 commit
  33. 23 Apr, 2004 1 commit
  34. 15 Apr, 2004 1 commit
  35. 14 Mar, 2004 1 commit