[Spice-commits] Changes to 'usb.5'

[Gerd Hoffmann]

New branch 'usb.5' available with the following commits:
commit ea87e95f8fda609fa665c2abd33c30ae65e6fae2
Author: Blue Swirl <blauwirbel at gmail.com>
Date:   Sun Jan 23 08:48:41 2011 +0000

    usb-bus: use snprintf
    
    Avoid this warning from OpenBSD linker:
      LINK  i386-softmmu/qemu
    ../usb-bus.o(.text+0x27c): In function `usb_get_fw_dev_path':
    /src/qemu/hw/usb-bus.c:294: warning: sprintf() is often misused,
    please use snprintf()
    
    Signed-off-by: Blue Swirl <blauwirbel at gmail.com>
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit ee59e6b3bf2074774a0626bc3d5389f2b7bd05bd
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Fri Dec 10 14:40:30 2010 +0100

    usb hid: add migration support
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit d15500902adb79034ef40ee3a06bbc0a7e0d8b19
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Wed Dec 15 12:45:24 2010 +0100

    usb hub: add migration support
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit c1ecb40a6124b80f1e346e38a1975e82da6507ca
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Fri Dec 10 14:20:46 2010 +0100

    usb core: add migration support
    
    Yes, seriously.  There is no migration support at all for usb devices.
    They loose state, especially the device address, and stop responding
    because of that.  Oops.
    
    Luckily there is so much broken usb hardware out there that the guest
    usually just kicks the device hard (via port reset and
    reinitialization), then continues without a hitch.  So we got away with
    that in a surprising high number of cases.
    
    The arrival of remote wakeup (which enables autosuspend support) changes
    that picture though.  The usb devices also forget that it they are
    supposed to wakeup, so they don't do that.  The host also doesn't notice
    the device stopped working in case it suspended the device and thus
    expects it waking up instead of polling it.  Result is that your mouse
    is dead.
    
    Lets start fixing that.  Add a vmstate struct for USBDevice.
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 9892088b52da05c3944e84982922fa984e048044
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Fri Jan 14 10:56:54 2011 +0100

    vnc: fix numlock+capslock tracking
    
    This patch makes the numlock+capslock tracking logic only look at
    keydown events.  Without this patch the vnc server will insert
    bogous capslock keypress in case it sees the following key sequence:
    
      shift down --- 'A' down --- shift up  --- 'A' up
                                             ^ here
    
    It doesn't hurt with a PS/2 keyboard, but it disturbs the USB Keyboard.
    And with the key event queue just added to the usb keyboard the guest
    will actually notice.
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 42292d4e51ac01eb28360d53127337fe275c39c5
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Fri Jan 14 09:23:22 2011 +0100

    usb hid: move head+n to common struct
    
    This patch moves the 'head' and 'n' fields from USBMouseState and
    USBKeyboardState to the common USBHIDState struct.
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 5fae51a9c26c025b94f8d7c40f54b65049de7227
Author: Gerd Hoffmann <kraxel at redhat.com>
Date:   Thu Jan 13 17:42:06 2011 +0100

    usb keyboard: add event event queue
    
    This patch adds a event queue to the usb keyboard.  This makes sure the
    guest will see all key events even if they come in bursts.  With this
    patch applied sending Ctrl-Alt-Del using vncviewer's F8 menu works.
    Also with autosuspend enabled the first keypress on a suspended keyboard
    takes a little longer to be delivered to the guest because the usb bus
    must be resumed first.  Without event queue this easily gets lost.
    
    Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

commit 13f8b97a57450534ccb7aaeb55095a668183fbee
Author: Paolo Bonzini <pbonzini at redhat.com>
Date:   Wed Jan 12 13:19:20 2011 +0100

    add event queueing to USB HID
    
    The polling nature of the USB HID device makes it very hard to double
    click or drag while on a high-latency VNC connection.  This patch,
    based on work done in the Xen qemu-dm tree by Ian Jackson, fixes this
    bug by adding an event queue to the device.  The event queue associates
    each movement with the correct button state, and remembers all button
    presses and releases as well.
    
    Signed-off-by: Ian Jackson <ian.jackson at eu.citrix.com>
    Signed-off-by: Stefano Stabellini <stefano.stabellini at eu.citrix.com>
    Signed-off-by: Paolo Bonzini <pbonzini at redhat.com>
    Signed-off-by: Gerd Hoffman <kraxel at redhat.com>