1. 29 Apr, 2016 1 commit
  2. 12 Nov, 2014 1 commit
  3. 29 Jul, 2014 1 commit
  4. 12 Jan, 2014 1 commit
  5. 10 Jul, 2012 2 commits
  6. 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
  7. 21 Sep, 2011 1 commit
  8. 06 May, 2011 2 commits
    • Daniel Stone's avatar
      XKB: Fix sense inversion for core MapNotify events · 3231962d
      Daniel Stone authored
      Due to an unfortunate sense inversion incident while switching from a
      if (foo) { ... } to if (!foo) continue; style in f06a9d, we punished any
      client who attempted to use XKB to restrict the MapNotify events they
      wanted by sending them exactly the events they _didn't_ want, and
      nothing else.
      
      NewKeyboardNotifies (coming from a client setting the map with an XKB
      request, when switching between master devices, etc) weren't affected,
      but this would impact anyone using xmodmap-style core requests.  Could
      explain a fair bit.
      
      Clarified the comments while I was at it.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      3231962d
    • Daniel Stone's avatar
      XKB: Send XKB events for all devices to all clients · 460a377e
      Daniel Stone authored
      We were using XIShouldNotify(client, device) as a test for whether or
      not to send XKB map/state/etc changed events, which limits it to only
      sending events for the current ClientPointer/ClientKeyboard for that
      client.  While this makes perfect sense for core events (e.g.
      MappingNotify), XKB events carry a device ID, so are safe to send to all
      clients for all devices.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      460a377e
  9. 25 Apr, 2011 1 commit
  10. 01 Sep, 2010 1 commit
  11. 19 May, 2010 1 commit
  12. 12 May, 2010 1 commit
  13. 21 Apr, 2010 1 commit
  14. 02 Feb, 2010 1 commit
  15. 24 Jan, 2010 1 commit
  16. 04 Sep, 2009 1 commit
  17. 08 May, 2009 1 commit
  18. 20 Mar, 2009 1 commit
  19. 16 Mar, 2009 1 commit
  20. 16 Feb, 2009 1 commit
  21. 22 Jan, 2009 2 commits
  22. 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
  23. 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
  24. 02 Dec, 2008 2 commits
  25. 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
  26. 04 Nov, 2008 2 commits
    • Peter Hutterer's avatar
      xkb: extract the correct device in XkbFilterEvents. · de1a8b68
      Peter Hutterer authored
      If the event is an XI event, we need to work on the correct device, not on
      the VCK.
      
      Adds XIGetDevice(event) function to extract the device from an event.
      de1a8b68
    • Peter Hutterer's avatar
      xkb: when faking mouse button events, fake them on the correct devices. · cbc6f983
      Peter Hutterer authored
      When MouseKeys are activated, keyboard devices may generate fake mouse button
      events through XKB. Let's get then running through the appropriate paths, i.e.
      as XI events on the correct device.
      
      To make matters more fun, ProcessOtherEvents drops events if the DIX device
      state cannot be updated accordingly, i.e. all button events from keyboard
      devices.
      Hence we need to get the paired MD for the device in XkbDDXFakeDeviceButton,
      and post the event through the paired MD (usually the VCP).
      
      Removes now-unused ddxFakeBtn.c.
      
      Note: this patch only half-arsedly fixed button events, motion events are a
      more complicated matter.
      cbc6f983
  27. 14 Jun, 2008 1 commit
  28. 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
  29. 17 Nov, 2007 1 commit
  30. 28 Oct, 2007 1 commit
    • Peter Hutterer's avatar
      xkb: enable XI event processing for xkb. · 99e826e8
      Peter Hutterer authored
      XI events can now take the same processing paths as core events, and should do
      the correct state changes etc.
      
      There's some cases where XKB will use KeyPress as type for an event to be
      delivered to the client. Stuck warnings in, not sure what the correct solution
      is yet.
      
      (cherry picked from commit 6334d4e7 with some
       additional compile fixes and non-MPX adaptations)
      99e826e8
  31. 28 Sep, 2007 1 commit
  32. 26 Sep, 2007 2 commits
  33. 20 Sep, 2007 1 commit
  34. 06 Sep, 2007 1 commit
    • Peter Hutterer's avatar
      xkb: enable XI event processing for xkb. · 6334d4e7
      Peter Hutterer authored
      XI events can now take the same processing paths as core events, and should do
      the correct state changes etc.
      
      There's some cases where XKB will use KeyPress as type for an event to be
      delivered to the client. Stuck warnings in, not sure what the correct solution
      is yet.
      6334d4e7