[The previous patch had a broken MIPS32R2 bitops implementation,
and was apparently too big to make it to the list. I retry now
with a compressed attachment.]
Hello All,
this patch adds support for all mandatory MIPS32R2 instructions,
rationalizes the instruction decoding to check always 32-bit
Hi,
On 28/11/06, Herbert Xu [EMAIL PROTECTED] wrote:
The default config read/write handlers allows a 4-byte read/write at
address 255. This can clobber the field after the config area. This
happens to be the PCIBus pointer in the PCIDevice structure.
An easier way to prevent the clobbering
The emulated CPU still identifies itself as a MIPS32(R1) 4Kc.
Currently it doesn't throw a RI exception for R2 instructions, this
is useful for Linux userland emulation, and also follows the current
policy which doesn't distinguish between MIPS32R1 instructions and
those of earlier ISAs.
I
Hi:
[QEMU] usb-uhci: Data buffer is too small
The data buffer is only 1280 bytes long but the user-supplied length
can be as large as 0x7ff. This patch extends the buffer to 2048
bytes.
Signed-off-by: Herbert Xu [EMAIL PROTECTED]
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email:
Hi guys,
I am using QEMU with Xen and Intel VT, and I have a question about
detecting the CD-ROM disk unmount event: When user ejects CD-ROM in the
guest domain, how can QEMU detect this event?
I know if we use info block command before and after a CD-ROM disk is
ejected, we can see the
On Thu, 2006-11-30 at 15:03 +0800, Yu, Xiaoyang wrote:
Hi guys,
I am using QEMU with Xen and Intel VT, and I have a question about
detecting the CD-ROM disk unmount event: When user ejects CD-ROM in
the guest domain, how can QEMU detect this event?
I know if we use “info block”
