1. 04 Jul, 2012 1 commit
  2. 06 Jun, 2012 1 commit
  3. 14 May, 2012 1 commit
  4. 21 Mar, 2012 1 commit
    • Keith Packard's avatar
      Introduce a consistent coding style · 9838b703
      Keith Packard authored
      
      
      This is strictly the application of the script 'x-indent-all.sh'
      from util/modular. Compared to the patch that Daniel posted in
      January, I've added a few indent flags:
      
      	-bap
      	-psl
      	-T PrivatePtr
      	-T pmWait
      	-T _XFUNCPROTOBEGIN
      	-T _XFUNCPROTOEND
      	-T _X_EXPORT
      
      The typedefs were needed to make the output of sdksyms.sh match the
      previous output, otherwise, the code is formatted badly enough that
      sdksyms.sh generates incorrect output.
      
      The generated code was compared with the previous version and found to
      be essentially identical -- "assert" line numbers and BUILD_TIME were
      the only differences found.
      
      The comparison was done with this script:
      
      dir1=$1
      dir2=$2
      
      for dir in $dir1 $dir2; do
      	(cd $dir && find . -name '*.o' | while read file; do
      		dir=`dirname $file`
      		base=`basename $file .o`
      		dump=$dir/$base.dump
      		objdump -d $file > $dump
      	done)
      done
      
      find $dir1 -name '*.dump' | while read dump; do
      	otherdump=`echo $dump | sed "s;$dir1;$dir2;"`
      	diff -u $dump $otherdump
      done
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Acked-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      9838b703
  5. 02 Oct, 2011 1 commit
  6. 22 Aug, 2011 1 commit
  7. 22 Feb, 2011 1 commit
  8. 02 Jul, 2010 1 commit
  9. 01 Jul, 2010 3 commits
    • Peter Hutterer's avatar
      xkb: release XTEST pointer buttons on physical releases. (#28808) · 14327858
      Peter Hutterer authored
      If a button release event is posted for the MD pointer, post a release event
      through the matching XTEST device. This way, a client who posts a button
      press through the XTEST extension cannot inadvertedly lock the button.
      
      This behaviour is required for historical reasons, until server 1.7 the core
      pointer would release a button press on physical events, regardless of the
      XTEST state. Clients seem to rely on this behaviour, causing seemingly stuck
      grabs.
      
      The merged behaviour is kept for multiple keyboard PointerKey events, if two
      physical keyboards hold the button down as a result of PointerKey actions,
      the button is not released until the last keyboard releases the button.
      
      X.Org Bug 28808 <http://bugs.freedesktop.org/show_bug.cgi?id=28808
      
      >
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      14327858
    • Peter Hutterer's avatar
      xkb: merge lockedPtrButtons state from all attached SDs. · 69ac9098
      Peter Hutterer authored
      
      
      Problem:
      lockedPtrButtons keeps the state of the buttons locked by a PointerKeys button
      press. Unconditionally clearing the bits may cause stuck buttons in this
      sequence of events:
      
      1. type Shift + NumLock to enable PointerKeys
      2. type 0/Ins on keypad to emulate Button 1 press
              → button1 press event to client
      3. press and release button 1 on physical mouse
              → button1 release event to client
      
      Button 1 on the MD is now stuck and cannot be released.
      
      Cause:
      XKB PointerKeys button events are posted through the XTEST pointer device.
      Once a press is generated, the XTEST device's button is down. The DIX merges
      the button state of all attached SDs, hence the MD will have a button down
      while the XTEST device has a button down.
      
      PointerKey button events are only generated on the master device to avoid
      duplicate events (see XkbFakeDeviceButton()). If the MD has the
      lockedPtrButtons bit cleared by a release event on a physical device, no
      such event is generated when a keyboard device triggers the PointerKey
      ButtonRelease trigger. Since the event - if generated - is posted through
      the XTEST pointer device, lack of a generated ButtonRelease event on the
      XTEST pointer device means the button is never released, resulting in the
      stuck button observed above.
      
      Solution:
      This patch merges the MD's lockedPtrButtons with the one of all attached
      slave devices on release events. Thus, as long as one attached keyboard has
      a lockedPtrButtons bit set, this bit is kept in the MD. Once a PointerKey
      button is released on all keyboards, the matching release event is emulated
      from the MD through the XTEST pointer device, thus also releasing the button
      in the DIX.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      69ac9098
    • Peter Hutterer's avatar
      xkb: remove now obsolete comment. · dbf249ec
      Peter Hutterer authored
      
      
      Looks like nothing broke from removing the hardcoded CoreProcessPointerEvent
      call. Whoop. Di. Doo.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      dbf249ec
  10. 30 Jun, 2010 1 commit
    • Keith Packard's avatar
      xkb: merge lockedPtrButtons state from all attached SDs. · 60527106
      Keith Packard authored
      
      
      Problem:
      lockedPtrButtons keeps the state of the buttons locked by a PointerKeys button
      press. Unconditionally clearing the bits may cause stuck buttons in this
      sequence of events:
      
      1. type Shift + NumLock to enable PointerKeys
      2. type 0/Ins on keypad to emulate Button 1 press
              → button1 press event to client
      3. press and release button 1 on physical mouse
              → button1 release event to client
      
      Button 1 on the MD is now stuck and cannot be released.
      
      Cause:
      XKB PointerKeys button events are posted through the XTEST pointer device.
      Once a press is generated, the XTEST device's button is down. The DIX merges
      the button state of all attached SDs, hence the MD will have a button down
      while the XTEST device has a button down.
      
      PointerKey button events are only generated on the master device to avoid
      duplicate events (see XkbFakeDeviceButton()). If the MD has the
      lockedPtrButtons bit cleared by a release event on a physical device, no
      such event is generated when a keyboard device triggers the PointerKey
      ButtonRelease trigger. Since the event - if generated - is posted through
      the XTEST pointer device, lack of a generated ButtonRelease event on the
      XTEST pointer device means the button is never released, resulting in the
      stuck button observed above.
      
      Solution:
      This patch merges the MD's lockedPtrButtons with the one of all attached
      slave devices on release events. Thus, as long as one attached keyboard has
      a lockedPtrButtons bit set, this bit is kept in the MD. Once a PointerKey
      button is released on all keyboards, the matching release event is emulated
      from the MD through the XTEST pointer device, thus also releasing the button
      in the DIX.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      60527106
  11. 10 Jun, 2010 1 commit
  12. 02 Feb, 2010 1 commit
  13. 02 Dec, 2009 1 commit
  14. 22 Sep, 2009 1 commit
  15. 14 Sep, 2009 1 commit
  16. 04 Sep, 2009 1 commit
  17. 29 Jul, 2009 1 commit
  18. 02 Jun, 2009 1 commit
  19. 22 May, 2009 1 commit
  20. 03 Mar, 2009 1 commit
  21. 23 Feb, 2009 3 commits
  22. 22 Jan, 2009 3 commits
  23. 20 Jan, 2009 1 commit
  24. 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
  25. 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
  26. 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
  27. 27 Jul, 2008 1 commit
  28. 23 Jul, 2008 1 commit
  29. 17 Jul, 2008 1 commit
  30. 25 Jun, 2008 1 commit
  31. 17 Feb, 2008 1 commit
    • Daniel Stone's avatar
      XKB: Remove a bunch of mad ifdefs · 534fc514
      Daniel Stone authored
      We have SEEK_SET and size_t, seriously.  Also use DebugF instead of
      ifdef DEBUG, and ditch a couple of random bits that were never used.
      534fc514
  32. 15 Jan, 2008 1 commit
  33. 28 Nov, 2007 1 commit
  34. 23 Nov, 2007 1 commit