xserver: Changes to 'input-fixes-for-1.4.1'

[Daniel Stone]

New branch 'input-fixes-for-1.4.1' available with the following commits:
commit 61d9fe340543c10bd862b39129955bd44d54a07d
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:36:46 2007 +0300

    XFree86: Don't build XF86VidMode and XF86Misc unless explicitly asked
    
    We've got a configure option for whether or not to build these, so might as
    well make them useful.
    (cherry picked from commit 08d9a83fee32696474181fd806eb457737eef72c)

commit a941326062cb492d7325f9d1382055a9c6a1bf80
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:36:09 2007 +0300

    XFree86: Run all input events through XKB
    
    Wrap all input events so that they run through XKB's ProcessKeyEvent.
    
    (cherry picked from commit 05e35dedf859333d04b1062bd68cb6541c5b8f67)

commit 5383057b4e845d5e38bff99c52af6cf8f2620f34
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:35:31 2007 +0300

    XKB: Add more bits to xkbsrv.h
    
    Add the device private index, given we use that in a macro here, and also the
    prototype for xkbUnwrapProc, since that's also useful.
    (cherry picked from commit e5ca837fef5cb92ecc0306895a7ee93b8b118b3b)

commit b61cd1f873d753d885298876d67808657a434b65
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:34:22 2007 +0300

    Xi: Include XI protocol header in exevents.h
    
    Make sure we have all the types we need to use this header.
    (cherry picked from commit 9f2d25d374e91ddc2240b072356ca41119ee62b5)

commit 9f3bafdf862b11b366a80294f36fc77ec4bdf53c
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:33:52 2007 +0300

    XFree86: Remove ridiculous SIGIO debugging
    
    YOU PRESSED A KEY
    AND AGAIN
    YOU RELEASED A KEY
    AND AGAIN
    YOU PRESSED A KEY
    AND AGAIN
    
    ... not so much.
    (cherry picked from commit 6730d7fd995accca648bb2a18b0674faa5292e91)

commit 5ae4db19caf7273bdc0bd87422cf72ac1b4a64be
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:32:47 2007 +0300

    XKB: Cope with all events in XkbProcessKeyboardEvent
    
    Cope with Xi and pointer events in the (now increasingly misnamed)
    XkbProcessKeyboardEvent.  If it's the wrong type, call through the wrapping
    chain to get out; else, process it.
    
    (cherry picked from commit 9c128a8da7f257adca1e91002f952fbcbb751eee)

commit bba4d8f6e0163fbe4313bad732ab1bfc166ff6c9
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:31:39 2007 +0300

    XKB: Don't update indicators on all devices, add missing include file
    
    Don't get XkbUpdateIndicators to update the indicators on all our devices: we
    already deal with that ourselves.
    Add exevents.h include to get more (proto)types.
    (cherry picked from commit 02accb3aa4de38f6e088611316b99e36d767692d)

commit ae9f75bb007bb9f66b8ac2a26b5861e723ed24f7
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Sat Oct 27 21:11:46 2007 +0300

    configure.ac: Only build VidMode and XF86Misc when we want it
    
    Don't build XF86VidMode and XF86Misc in XFree86 dixmods even when we've
    explicitly asked not to, or just don't have them.
    
    (cherry picked from commit fdb2fd76f6cfa10f6b1b928e466bd35b4574e6cc)

commit 542d709f8a288621aba2eddae4f3fe5888741385
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Fri Oct 26 09:12:15 2007 +0300

    XFree86 Misc/VidMode: Remove ridiculous debug ErrorFs
    
    When we're building with --enable-debug, don't emit an ErrorF every time a
    function gets called.
    (cherry picked from commit 6d59bb5709a99ab60b482bbf3393ebffda7f9407)

commit 89c7ebfe8cce82d37b373627358a2cec46423f39
Author: Adam Jackson <ajax at benzedrine.nwnk.net>
Date:   Tue Sep 11 11:37:06 2007 -0400

    Ignore - not just block - SIGALRM around Popen()/Pclose().
    
    Because our "popen" implementation uses stdio, and because nobody's stdio
    library is capable of surviving signals, we need to make absolutely sure
    that we hide the SIGALRM from the smart scheduler.  Otherwise, when you
    open a menu in openoffice, and it recompiles XKB to deal with the
    accelerators, and you popen xkbcomp because we suck, then the scheduler
    will tell you you're taking forever doing something stupid, and the
    wait() code will get confused, and input will hang and your CPU usage
    slams to 100%.  Down, not across.
    (cherry picked from commit a5b8053606d6e786cdcf6734f271acc05f9cc588)

commit 85e24935737b77dece0cc004a441111ac7e6fe6b
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Fri Oct 26 09:10:04 2007 +0300

    Compile and warning fixes (DO NOT PUSH)

commit 4a4c6bbee7b9d38621f9d4e5ee37c84c87480947
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Fri Oct 26 09:09:53 2007 +0300

    Compile fix (IS THIS RIGHT??)

commit 6c769a23be0334996f05799a6c177d65adecf9c4
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Fri Oct 26 09:09:33 2007 +0300

    Compile fixes (DO NOT PUSH)

commit 2c9ce87d3989f60be74fa36660a3752c7e7b84dd
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Thu Sep 27 11:44:03 2007 +0930

    xkb: xkbHandleActions: let wrapping take care of event delivery.
    
    This is hopefully better than hardcodey calling CoreProcessPointerEvent.
    (cherry picked from commit 32d0440c7f6e604807cb14dd32349df6f22c903b)

commit ec4276878744215f18d34e9d0c21c8e62e278284
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Wed Sep 26 18:04:59 2007 +0930

    xkb: Unwrap properly in ProcessPointerEvent.
    
    Instead of hardcoding CoreProcessPointerEvent, actually try to unwrap properly
    and then call the unwrapped processInputProc. Seems to be a better idea,
    especially since it makes stuff actually work...
    (cherry picked from commit 8f9bf927e1beecf9b9ec8877131ec12c765e4d84)

commit c60d5694f611d7fa6638172b25ff291e663c8342
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Wed Sep 26 18:03:21 2007 +0930

    Xi: fix the wrapper code for processInputProc wrapping.
    
    Followup to [1].
    If a core grab causes the device to freeze, it overwrites the processInputProc
    of the device. [1] would then overwrite this while unwrapping, the device
    does not thaw anymore.
    Changing this to only re-wrap if the processInputProc hasn't been changed
    during the event handling.
    
    [1] 340911d7243a7f1095d79b5b2dcfa81b145c2474

commit a614a3ab397b302af761f939411dce2ee7be6f67
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Wed Sep 26 18:01:17 2007 +0930

    xfree86: pass in the XKB event processing proc instead of the XI one.
    
    We need to pass ProcessPointerEvent or ProcessKeyboardEvent to
    XkbSetExtension, otherwise we lose the xkb layer.

commit 7a6caf63ceaf4a7b2316013a250b18b6c8950f22
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Wed Sep 12 17:40:11 2007 +0930

    dix: don't compress motion events from different devices (EventEnqueue)

commit 5ab9cbec1a2e35cb0e57686df0bd103a174edf00
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Thu Sep 6 18:57:00 2007 +0930

    xfree86: wrap keyboard devices for XKB.
    
    Call ProcessOtherEvents first, then for all keyboard devices let them be
    wrapped by XKB. This way all XI events will go through XKB.
    
    Note that the VCK is still not wrapped, so core events will bypass XKB.

commit 87d46b9336dc994649556488b5b6b17d40885624
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Thu Sep 6 18:52:02 2007 +0930

    dix: add XI event support to FixKeyState.
    
    FixKeyState needs to be able to handle XI events, otherwise we get "impossible
    keyboard events" on server zaps and other special key combos.
    (cherry picked from commit 5ee409794ee604fcf84886f70429fc2d6b1ff4f1)

commit e4c28ecacee6fa6a0e714dd0702be3a82ec12232
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Thu Sep 6 18:49:57 2007 +0930

    xkb: enable XI event processing for xkb.
    
    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.

commit ddaafa3fb8443d4dc4307e1e75e7d3dfe485e847
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Thu Jun 21 18:24:30 2007 +0930

    Save processInputProc before wrapping it and restore it later, instead of
    using a hardcoded ProcessKeyboardEvent. Otherwise we lose the ability to
    process DeviceKeyEvents after the first key press.
    
    This should be the correct fix now.
    (cherry picked from commit 4d5df14f2c4a3108a8c8adfcf4766c0d1a9daad2)

commit f4fff77cd5b0b2889dfb7c46a5c7092cf33f3fa8
Author: Peter Hutterer <peter at cs.unisa.edu.au>
Date:   Tue Sep 4 17:44:51 2007 +0930

    xkb: Store the action filters per device in the XkbSrvInfoRec.
    
    Using a global array for action filters is bad. If two keyboard hit a modifier
    at the same time, releaseing the first one will deactivate the filter and
    thus the second keyboard can never release the modifier again.
    (cherry picked from commit bfe6b4d2d9952a80f8dbc63eec974ef894e5c226)

commit 720b536ee69de7d484da8f340814e1f1a1b7f83f
Author: Naoki Hamada <nao at tom-yam.or.jp>
Date:   Thu Oct 25 18:45:50 2007 +0300

    Input: Fix key down test (bug #12858)
    
    Fix the botched previous key_is_down test, which would give false positives.
    Also move key_autorepeats to a separate inline function.
    (cherry picked from commit 242f56f722243938e908d1957781ee53c2999783)