Woohoo!
Thanks to everybody on the quick turnaround on this,
it's very exciting to see it booting now. :)
- Eric
--- Fabrice Bellard <[EMAIL PROTECTED]> wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Fabrice Bellard06/09/29
> 20:01:17
>
> Modified files:
>
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/09/29 20:01:17
Modified files:
target-i386: helper.c
Log message:
32 bit RSP update fix (aka Open Solaris x86_64 bug)
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-i38
On Friday 29 September 2006 18:52, K. Richard Pixley wrote:
> When I build qemu-0.8.2, qemu-arm is a shared library rather than being
> an executable. This seems highly suspicious and makes it particularly
> difficult to debug. What's the rationale behind this?
http://www.qemu.org/qemu-tech.html
When I build qemu-0.8.2, qemu-arm is a shared library rather than being
an executable. This seems highly suspicious and makes it particularly
difficult to debug. What's the rationale behind this?
--rich
___
Qemu-devel mailing list
Qemu-devel@nongn
I saw the file src/hw/lance.c. Is it the driver for
amdlance NIC (as the one emulated in vmware)?
I don't know what vmware emulates, but the Lance NIC for Sparc32 is based on
Am7990. In the CVS version it was merged with PCNet driver, because
Am79C970A is fully downwards compatible towards Am7
On Tuesday 26 September 2006 19:27, Martin Guy wrote:
> Summary:
> Ever since QEMU 0.8.1, qemu-arm-system mode works fine with ARM EABI
> kernel and rootfs, but qemu-arm single-process mode is broken with
> EABI, failing with "Unknown system call 0xf0005".
> This is ARM private system call "set
- Voipio's "eabi-rootfs" which I gather uses EABI internally and glibc
shims to convert the system calls to old-ABI just before they hit the
kernel (glibc-2.3.4)
I have a similar setup with a maemo 2.0 rootstrap (glibc 2.3.5). I am
currently able to compile a functional python package. I am not
Am 29.08.2006 um 00:29 schrieb Fabrice Bellard:
Hi,
Mike Kronenberg wrote:
@Fabrice
How are your plans about supporting OS X in the future?
We, for our part, are eager to push dev on OS X:
- with the patches of Gwenole and pbrook, qemu 0.8.2 builds great
on OS X ppc and intel (gcc4). All t
2006/9/26, Martin Guy <[EMAIL PROTECTED]>:
Ever since QEMU 0.8.1, qemu-arm-system mode works fine with ARM EABI
kernel and rootfs, but qemu-arm single-process mode is broken with
EABI, failing with "Unknown system call 0xf0005".
Fixed for simple cases by pbrook's preliminary patches mentioned
There are some statistics at freaknet.org/martin/QEMU for various
are in cluster.aleph1.co.uk/~martin/qemu.html (please ignore the other
Sorry, that first page is bogus. I meant the second.
M
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http
> If I run qemu for i386 without kqemu it uses soft-mmu, so it operates as
> another architetture as ppc or mips right?
> So... are the performace of qemu the same if I use i386 or mips or something
> change deeply?
> Example: if I run the same program on i386 emulation without kqemu or on
> mips
Summary:
Ever since QEMU 0.8.1, qemu-arm-system mode works fine with ARM EABI
kernel and rootfs, but qemu-arm single-process mode is broken with
EABI, failing with "Unknown system call 0xf0005".
This is ARM private system call "set_tls", called from both the
linuxthreads and the NPTL pthread imp
On Wed, Sep 06, 2006 at 12:14:44PM +0200, Aurelien Jarno wrote:
I have setup a debian arm (unstable) under QEMU, until now using version
0.8.1 and a root on NFS.
I wanted to use the new SCSI card emulation introduced in QEMU 0.8.2,
but it fails to boot (still with root on NFS). It freeze, the la
Anyone else noticed qemu crash with Windows XP guest and pdf creation
software?
Prerequisites:
Windows XP (any SP level)
Adobe Acrobat Profesional 7.xx OR Nitro PDF
Qemu 0.8.2 (without kqemu)
Symptons:
Launcing any of the apps crash the app (with Adobe Acrobat Pro it's in
module
Technical det
Hello,
Quite a dilema here,
my objective is to execute a linux x86 binary on an
linux arm host.
I played with the qemu tarball relentlessly and I am
not capable of getting qemu compiled with a arm target
to support i386-user.
Is it possible to get qemu to compile with an arm gcc
compiler?
If
TLS and multithreaded applications are known to not work with usermode
emulation.
In the end, it was an uninitialized stack allocated variable in libc
that was causing this problem
(http://sources.redhat.com/ml/libc-alpha/2006-09/msg00063.html).
Paul
Thanks,
Rafael
___
Tom Marn wrote:
Here is my modified translate.c (still broken code)
Re-sending previous malformed patch (I hope this one will be formated ok).
--- target-ppc/translate.c.orig 2006-09-29 09:29:28.0 +0200
+++ target-ppc/translate.c 2006-09-29 09:39:17.0 +0200
@@ -1715,21 +171
Hi
I'm using QEMU to emulate PowerPC 603e for testing my cross compiled root filesystem on i686.
When executing binary which is compiled (without -msoft-float) to use full floating point instruction set,
kernel returns "Illegal instruction" at runtime. After core dump debugging my
binary I fou
18 matches
Mail list logo
