From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc64 progress
Date: Wed, 16 Jul 2008 11:24:58 +0300 [thread overview]
Message-ID: <f43fc5580807160124s6211ae37mf1c98458e18a0d71@mail.gmail.com> (raw)
In-Reply-To: <20080716080128.GA6915@vimes.madsworld.lan>
On 7/16/08, Markus Dahms <mad@automagically.de> wrote:
> Hi,
>
> > With Qemu r4780 and OpenBIOS r201 I get the following output on serial
> > console:
> > ./qemu-system-sparc64 -L . -kernel vmlinux-2.6.25.10-sun4u -serial stdio
>
>
> nice progress. Sadly I can't reproduce it here (still ia32, gcc-3.4), gdb
> isn't really helpful for me:
>
> | $ gdb qemu-system-sparc64
> | (gdb) run -L . -kernel vmlinuz-2.6.18-6-sparc64-smp -serial stdio
> | OpenBIOS for Sparc64
> |
> | Program received signal SIGSEGV, Segmentation fault.
> | [Switching to Thread 0xb7b306b0 (LWP 7734)]
> | 0x08146ea3 in ?? ()
> | (gdb) bt
> | #0 0x08146ea3 in ?? ()
> | #1 0xab2a95a8 in ?? ()
> | #2 0x0891f204 in ?? ()
> | #3 0x00000000 in ?? ()
> | (gdb)
>
> You may find a log with "-d op,exec,cpu,out_asm,in_asm,int" at
> http://automagically.de/files/qemu-sparc64.log (~ 1.4 MB)
>
> For the longer term, do you plan to add support for the SBus-based
> Sun4u machines? At least for the Ultra 1 most of the hardware is
> already emulated for Sun4m (esp, le, cg6...)... For the U1E/U2
> isn't much needed either (hme, perhaps some fas bits in esp)...
> Just a lot of glue missing ;)
Well, for now I try to get things working on a maximally PC-like
system (PCI, IDE, VGA, serial). After that (or if the approach fails)
more machines could be added.
prev parent reply other threads:[~2008-07-16 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 15:15 [Qemu-devel] Sparc64 progress Blue Swirl
2008-07-16 7:26 ` Mulyadi Santosa
2008-07-16 7:38 ` Jonathan Kalbfeld
2008-07-16 7:54 ` Aurelien Jarno
2008-07-16 8:18 ` Blue Swirl
2008-07-16 17:18 ` Blue Swirl
2008-07-17 19:48 ` Blue Swirl
2008-07-16 8:01 ` Markus Dahms
2008-07-16 8:24 ` Blue Swirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580807160124s6211ae37mf1c98458e18a0d71@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).