1. 20 Jan, 2014 1 commit
  2. 02 Dec, 2013 1 commit
  3. 27 Aug, 2013 1 commit
  4. 22 Jul, 2013 1 commit
    • Jan Kiszka's avatar
      gtk: Fix accelerator filtering · b1e749c0
      Jan Kiszka authored
      This is in fact very simply: When the input in grabbed, everything
      should be exclusively passed to the guest - except it has our magic
      CTRL-ALT modifier set. Then let GTK filter out those accels that are in
      use. When checking the modifier state, we just need to filter out NUM
      and CAPS lock.
      
      Note: Filtering based on hard-coded modifiers breaks overriding
      accelerators. Needs to be fixed at a later point.
      Signed-off-by: default avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      b1e749c0
  5. 28 Jun, 2013 1 commit
    • Gerd Hoffmann's avatar
      gtk: add support for surface conversion · f0875536
      Gerd Hoffmann authored
      Also use CAIRO_FORMAT_RGB24 unconditionally.  DisplaySurfaces will never
      ever see 8bpp surfaces.  And using CAIRO_FORMAT_RGB16_565 for the 16bpp
      case doesn't seem to be a good idea too.
      
      <quote src="/usr/include/cairo/cairo.h">
       * @CAIRO_FORMAT_RGB16_565: This format value is deprecated. It has
       *   never been properly implemented in cairo and should not be used
       *   by applications. (since 1.2)
      </quote>
      Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
      Message-id: 1372150134-8590-1-git-send-email-kraxel@redhat.com
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      f0875536
  6. 17 Jun, 2013 1 commit
    • Stefan Weil's avatar
      gtk: Fix compiler warning (GTK 3 deprecated function) · 030b4b7d
      Stefan Weil authored
      With GTK 3, the function gdk_cursor_unref is deprecated:
      
      qemu/ui/gtk.c: In function ‘gd_cursor_define’:
      qemu/ui/gtk.c:380:5: error:
       ‘gdk_cursor_unref’ is deprecated (declared at /usr/include/gtk-3.0/gdk/gdkcursor.h:233): Use 'g_object_unref' instead [-Werror=deprecated-declarations]
      
      Fix the gcc compiler warning by using conditional compilation.
      Signed-off-by: default avatarStefan Weil <sw@weilnetz.de>
      Message-id: 1371391987-10795-1-git-send-email-sw@weilnetz.de
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      030b4b7d
  7. 14 Jun, 2013 1 commit
    • Michael Tokarev's avatar
      create qemu_openpty_raw() helper function and move it to a separate file · 4efeabbb
      Michael Tokarev authored
      In two places qemu uses openpty() which is very system-dependent,
      and in both places the pty is switched to raw mode as well.
      Make a wrapper function which does both steps, and move all the
      system-dependent complexity into a separate file, together
      with static/local implementations of openpty() and cfmakeraw()
      from qemu-char.c.
      
      It is in a separate file, not part of oslib-posix.c, because
      openpty() often resides in -lutil which is not linked to
      every program qemu builds.
      
      This change removes #including of <pty.h>, <termios.h>
      and other rather specific system headers out of qemu-common.h,
      which isn't a place for such specific headers really.
      
      This version has been verified to build correctly on Linux,
      OpenBSD, FreeBSD and OpenIndiana.  On the latter it lets qemu
      to be built with gtk gui which were not possible there due to
      missing openpty() and cfmakeraw().
      Signed-off-by: default avatarMichael Tokarev <mjt@tls.msk.ru>
      Tested-by: default avatarAndreas Färber <andreas.faerber@web.de>
      4efeabbb
  8. 11 Jun, 2013 1 commit
  9. 10 Jun, 2013 2 commits
    • Michael Roth's avatar
      qemu-char: don't issue CHR_EVENT_OPEN in a BH · bd5c51ee
      Michael Roth authored
      When CHR_EVENT_OPENED was initially added, it was CHR_EVENT_RESET,
      and it was issued as a bottom-half:
      
      86e94dea
      
      Which we basically used to print out a greeting/prompt for the
      monitor.
      
      AFAICT the only reason this was ever done in a BH was because in
      some cases we'd modify the chr_write handler for a new chardev
      backend *after* the site where we issued the reset (see:
      86e94d:qemu_chr_open_stdio())
      
      At some point this event was renamed to CHR_EVENT_OPENED, and we've
      maintained the use of this BH ever since.
      
      However, due to 9f939df9, we schedule
      the BH via g_idle_add(), which is causing events to sometimes be
      delivered after we've already begun processing data from backends,
      leading to:
      
       known bugs:
      
        QMP:
          session negotation resets with OPENED event, in some cases this
          is causing new sessions to get sporadically reset
      
       potential bugs:
      
        hw/usb/redirect.c:
          can_read handler checks for dev->parser != NULL, which may be
          true if CLOSED BH has not been executed yet. In the past, OPENED
          quiesced outstanding CLOSED events prior to us reading client
          data. If it's delayed, our check may allow reads to occur even
          though we haven't processed the OPENED event yet, and when we
          do finally get the OPENED event, our state may get reset.
      
        qtest.c:
          can begin session before OPENED event is processed, leading to
          a spurious reset of the system and irq_levels
      
        gdbstub.c:
          may start a gdb session prior to the machine being paused
      
      To fix these, let's just drop the BH.
      
      Since the initial reasoning for using it still applies to an extent,
      work around that by deferring the delivery of CHR_EVENT_OPENED until
      after the chardevs have been fully initialized, toward the end of
      qmp_chardev_add() (or some cases, qemu_chr_new_from_opts()). This
      defers delivery long enough that we can be assured a CharDriverState
      is fully initialized before CHR_EVENT_OPENED is sent.
      
      Also, rather than requiring each chardev to do an explicit open, do it
      automatically, and allow the small few who don't desire such behavior to
      suppress the OPENED-on-init behavior by setting a 'explicit_be_open'
      flag.
      
      We additionally add missing OPENED events for stdio backends on w32,
      which were previously not being issued, causing us to not recieve the
      banner and initial prompts for qmp/hmp.
      Reported-by: default avatarStefan Priebe <s.priebe@profihost.ag>
      Signed-off-by: default avatarMichael Roth <mdroth@linux.vnet.ibm.com>
      Message-id: 1370636393-21044-1-git-send-email-mdroth@linux.vnet.ibm.com
      Cc: qemu-stable@nongnu.org
      Signed-off-by: default avatarMichael Roth <mdroth@linux.vnet.ibm.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      bd5c51ee
    • Anthony Liguori's avatar
      gtk: use better icon · f7da9c17
      Anthony Liguori authored
      The current icon looks pretty terrible rendered in Gnome.  This
      switches to a transparent SVG which looks much nicer.
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      f7da9c17
  10. 03 Jun, 2013 2 commits
  11. 14 May, 2013 1 commit
  12. 13 May, 2013 1 commit
  13. 26 Apr, 2013 1 commit
  14. 25 Apr, 2013 1 commit
  15. 23 Apr, 2013 1 commit
  16. 17 Apr, 2013 1 commit
  17. 16 Apr, 2013 3 commits
  18. 15 Apr, 2013 1 commit
  19. 02 Apr, 2013 2 commits
  20. 27 Mar, 2013 1 commit
  21. 25 Mar, 2013 1 commit
  22. 18 Mar, 2013 5 commits
  23. 13 Mar, 2013 1 commit
  24. 26 Feb, 2013 8 commits