From: "Blue Swirl" <blauwirbel@gmail.com>
To: Jakub Jermar <jakub@jermar.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed
Date: Thu, 28 Aug 2008 19:30:23 +0300 [thread overview]
Message-ID: <f43fc5580808280930j524a8d7cy801cadf09640624b@mail.gmail.com> (raw)
In-Reply-To: <48B6CD69.5020101@jermar.eu>
On 8/28/08, Jakub Jermar <jakub@jermar.eu> wrote:
> Blue Swirl wrote:
> <snip>
>
> > What host? On my amd64 and using the latest OpenBIOS I get this:
> >
>
> Oops, the host is ia32 and the OpenBIOS is the one from qemu's current
> trunk. I will try it on amd64 shortly.
It should work on i386 too. It just seems that some bugs on i386 can't
be reproduced on amd64 32-bit chroot.
> Btw, couldn't you update the openbios version in qemu? It will allow me
> to make sure that HelenOS on qemu/sparc64 makes it to the point where
> it probes the framebuffer and eventually write a small driver for it.
Well, if the firmware configuration device is committed, I'll update
OpenBIOS to the new system and then probably update the image.
I wouldn't trust the Qemu version of VGA on Sparc64 yet, there could
be some wrong assumptions. Once a real kernel can boot, initialize the
VGA and preferably start X, then we should know that it's realistic.
next prev parent reply other threads:[~2008-08-28 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 12:55 [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed Jakub Jermar
2008-08-28 15:57 ` Blue Swirl
2008-08-28 16:08 ` Jakub Jermar
2008-08-28 16:30 ` Blue Swirl [this message]
2008-08-28 16:59 ` Jakub Jermar
2008-08-28 17:16 ` Blue Swirl
2008-08-28 19:05 ` Blue Swirl
2008-08-29 18:37 ` Blue Swirl
2008-08-29 19:22 ` Paul Brook
2008-08-29 19:54 ` Blue Swirl
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=f43fc5580808280930j524a8d7cy801cadf09640624b@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jakub@jermar.eu \
--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).