qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: aurelien@aurel32.net
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Updated OpenBIOS images
Date: Mon, 16 Apr 2007 17:40:55 +0300	[thread overview]
Message-ID: <f43fc5580704160740v6afd61f0q3af88da51d2a611f@mail.gmail.com> (raw)
In-Reply-To: <46230AD0.4080609@aurel32.net>

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

On 4/16/07, Aurelien Jarno <aurelien@aurel32.net> wrote:
> Blue Swirl a écrit :
> > The Sparc64 image can be booted using either VGA or serial. In both
> > cases, entering the Forth interpreter fails.
> >
>
> Is it possible (even hackish) to ignore openbios an jump directly to the
> kernel when using -kernel?

You can try this patch. It bypasses the Forth setup and jumps to a
hard coded kernel start address.

[-- Attachment #2: sparc64-kernel.diff --]
[-- Type: text/x-patch, Size: 665 bytes --]

Index: openbios-quilt/arch/sparc64/openbios.c
===================================================================
--- openbios-quilt.orig/arch/sparc64/openbios.c	2007-04-14 19:39:24.000000000 +0000
+++ openbios-quilt/arch/sparc64/openbios.c	2007-04-16 14:34:45.000000000 +0000
@@ -112,7 +112,13 @@
 #ifdef CONFIG_DEBUG_BOOT
 	printk("done\n");
 #endif
+        {
+            int (*entry)(const void *romvec, int p2, int p3, int p4, int p5);
 
+            printk("[sparc64] Kernel already loaded\n");
+            entry = (void *) 0x404000;
+            entry(0, 0, 0, 0, 0);
+        }
 	PUSH_xt( bind_noname_func(arch_init) );
 	fword("PREPOST-initializer");
 	

      parent reply	other threads:[~2007-04-16 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15  7:09 [Qemu-devel] Updated OpenBIOS images Blue Swirl
2007-04-16  5:34 ` Aurelien Jarno
2007-04-16 14:16   ` Peter
2007-04-16 14:40   ` 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=f43fc5580704160740v6afd61f0q3af88da51d2a611f@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=aurelien@aurel32.net \
    --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).