Hi,
[please keep me CCed, I'm not on this list]
the below patch let's qemu be compiled by GCC 4.2 (probably also 4.1 and
others) for most hosts (i386,x86_64,ia64,ppc). s390 as host is missing,
and needs a compiler change to emit the literal store inline again, as the
literal pool at the end f
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/08/28 22:21:41
Modified files:
. : vl.c
Log message:
Build fix for older GCCs.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/vl.c?cvsroot=qemu&r1=1.335&r2=1.336
> On second thought, there is a huge difference between a write access
> originating from CPU destined for the device and the device writing to
> main memory. The CPU address could be 0xf000 1000, which may translate
> to a bus address of 0x1000, as an example. The device could write to
> main memo
On 8/26/07, Blue Swirl <[EMAIL PROTECTED]> wrote:
> On 8/26/07, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
> > Paul Brook wrote:
> > pci_gdma.diff: Convert PCI devices and targets
> >
> > Any comments? The patches are a bit intrusive and I can't test the
> > targets except that
Hi,
I have been investigating why Coherent (a discontinued UNIX clone)
doesn't boot in QEMU (and in Bochs, VirtualBox, VirtualPC, etc.).
The reason for this is a weird format detection routine used by its
floppy driver. To check whether the sectors of the disk are interleaved
and to determine
This patch adds a QEMU monitor command may switch the domain owning the
physical cdrom, such that an eject command on the guest command line
will physically eject the drive door.
Monitor command example:
set_cdrom_owner 1 hdd
(for the time being the "hdd" parameter is a constant, as we only
s
Hi, I have been using QEMU's VNC support quite extensively since 0.8.1
came out, and every once in a while QEMU froze on me while interacting
with a guest OS through a VNC client. I recently spent some time
tracking down this bug in QEMU 0.9.0 and I found and fixed it in vnc.c
(see patch below).
I
