Hi,
the qemu documentation states about sparc emulation: "... Please note
that currently NetBSD, OpenBSD or Solaris kernels don't work."
What's needed to get Solaris to word? Or any of the BSDs?
Regards
Markus
___
Qemu-devel mailing list
Qemu-dev
Hi all,
I have a system arm from scratch and I'm running a chroot all over
qemu user mode emulation and getting the following problem:
"Function not implemented" message error when try something recursive...
detailing:
# creating files
bash-3.2# mkdir /tmp/dir
bash-3.2# touch /tmp/dir/file1
bas
There are a number of bugs in OpenBIOS, and at least one in qemu.
Your best bet is to check the OpenBIOS mailing list, where I've
discussed a number of the OpenBIOS issues.
On 2/27/07, Markus Schiltknecht <[EMAIL PROTECTED]> wrote:
Hi,
the qemu documentation states about sparc emulation: "... P
hw/sun4m.c, line 154:
m48t59_write(nvram, i++, 0x80); /* Sun4m OBP */
This is not a machine type recognized by SunOS (and probably other
early versions of Solaris). According to idprom.h (some which is
quoted at http://www.sunmanagers.org/archives/1993/0050.html), the
only recognized sun4m I
> -Original Message-
> From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> rg] On Behalf Of Peter
> Sent: 27 February 2007 14:55
> To: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] running (open) solaris on sparc32
>
> There are a number of bugs in OpenBIOS, and at least one in q
Hi all,
I've just noticed that qemu does not has the at() syscalls support
implemented yet...
Does anyone has a patch that implements these syscalls:
.long sys_openat/* 295 */
.long sys_mkdirat
.long sys_mknodat
.long sys_fchownat
.long sys_futimesat
.long sys_fstatat64 /* 300 *
It would be great to see Hervé's patch in CVS HEAD.
There are already emulated MIPS machines with and without
FPU today, so removing the need for different binaries
is a good idea.
Stefan
Hervé Poussineau schrieb:
> Hi,
>
> This patch remove (most of) the use of the #define MIPS_USES_FPU, and
>
A new PCI network card is emulated partially with QEMU:
the wireless LAN adapter TNETW1130 (ACX111).
I needed this driver as a debugging aid for existing (AR7) hardware
with the Open Source ACX111 driver for Linux.
So my main focus are debug messages from this driver, not real
network emulation
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer 07/02/27 19:27:51
Modified files:
target-mips: op.c translate.c
Log message:
Fix mips FPU emulation, 32 bit data types are allowed to use odd
registers.
CVSWeb URLs:
http://cvs.savannah.gn
hw/sun4m.c, line 154:
m48t59_write(nvram, i++, 0x80); /* Sun4m OBP */
This is not a machine type recognized by SunOS (and probably other
early versions of Solaris). According to idprom.h (some which is
quoted at http://www.sunmanagers.org/archives/1993/0050.html), the
only recognized sun4m I
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/02/27 21:02:54
Modified files:
. : Makefile.target
Log message:
Include LDFLAGS when linking system emulator.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/Makefile.target?
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 07/02/27 21:04:49
Modified files:
. : configure
Log message:
Compiler check for byteswap.h instead of hardcoded path.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/configure?c
the qemu documentation states about sparc emulation: "... Please note that
currently NetBSD, OpenBSD or Solaris kernels don't work."
What's needed to get Solaris to word? Or any of the BSDs?
OpenBIOS for Qemu was developed against Linux, which does not need too much
from the BIOS. Other kerne
On 27 févr. 07, at 08:22, Ilya Shar wrote:
Please see the diff file attached.
I meant send a diff to the qemu-devel in a new mail with [Patch] in
the subject so that it can be committed :-)
However, at second thought, I think that it might need some re-work,
see [1], and the arguments m
Hello,
I'm trying to use ddd (connected to QEMU) to debug my own kernel and it works
fine.
The only problem I have is that I'm always interrupted by my IRQ handlers (and
especially the timer, IRQ 0).
Is there a way to avoid ddd to jump to my irq handlers functions so I can step
into my code
On Wednesday 28 February 2007 03:11, Gregory Cavelier wrote:
> I'm trying to use ddd (connected to QEMU) to debug my own kernel and it
> works fine.
>
> The only problem I have is that I'm always interrupted by my IRQ handlers
> (and especially the timer, IRQ 0).
>
> Is there a way to avoid ddd to
16 matches
Mail list logo