1. 12 1月, 2011 14 次提交
  2. 11 1月, 2011 13 次提交
  3. 10 1月, 2011 1 次提交
  4. 07 1月, 2011 3 次提交
  5. 05 1月, 2011 2 次提交
    • A
      cirrus_vga: fix division by 0 for color expansion rop · 92d675d1
      Aurelien Jarno 提交于
      Commit d85d0d38 introduces a regression
      with Windows ME that leads to a division by 0 and a crash.
      
      It uses the color expansion rop with the source pitch set to 0. This is
      something allowed, as the manual explicitely says "When the source of
      color-expand data is display memory, the source pitch is ignored.".
      
      This patch fixes this regression by computing sx, sy and others
      variables only if they are going to be used later, that is for a plain
      copy ROP. It basically consists in moving code.
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      92d675d1
    • A
      Fix curses on big endian hosts · 9ae19b65
      Aurelien Jarno 提交于
      On big endian hosts, the curses interface is unusable: the emulated
      graphic card only displays garbage, while the monitor interface displays
      nothing (or rather only spaces).
      
      The curses interface is waiting for data in native endianness, so
      console_write_ch() should not do any conversion. The conversion should
      be done when reading the video buffer in hw/vga.c. I supposed this
      buffer is in little endian mode, though it's not impossible that the
      data is actually in guest endianness. I currently have no big endian
      guest to way (they all switch to graphic mode immediately).
      Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
      9ae19b65
  6. 27 12月, 2010 1 次提交
    • M
      pci: fix migration path for devices behind bridges · a6a7005d
      Michael S. Tsirkin 提交于
      The device path used for migration is currently broken for
      for all devices behind a nested bridge.
      
      Replace this by a hierarchical list of slot/function numbers, walking
      the path from root down to device. Add :00 after the domain number
      so that if there are no nested bridges, this is compatible
      with what we have now.
      
      Note: as pointed out by Gleb, using openfirmware paths
      might be cleaner, doing this would break compatibility though,
      and the IDs used are not guest or user visible at all,
      so breaking the compatibility is probably not worth it.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      a6a7005d
  7. 26 12月, 2010 1 次提交
  8. 24 12月, 2010 3 次提交
  9. 22 12月, 2010 2 次提交