qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add more devices for MIPS system emulation
Date: Sat, 11 Mar 2006 21:25:04 +0000	[thread overview]
Message-ID: <200603112125.05107.paul@codesourcery.com> (raw)
In-Reply-To: <20060306145044.GB27785@networkno.de>

> I updated the patch to allow for that again, and added an ELF loader on
> top to avoid hardcoded kernel load addresses/entry points. This is also
> useful for stand-alone programs. The ramdisk and command line addresses
> are still hardcoded.

Except now you can't load raw kernel images.

I'm still not convinced the boot sector hacks can do anything useful How 
exactly are you using these? You say the DECstation bios uses offsets stored 
in the boot sector to locate the second stage bootloader, but:
a) We aren't using a DECstation bios. I'm guessing we're not emulating 
DECstation hardware, so it wouldn't work even if we did have one.
b) You haven't modified the boot sector to provide those offsets.
c) You're only replacing the boot sector itself. Even if you did insert the 
correct offsets they'd still be pointing to random bits of user data, not the 
kernel you want to boot.

Paul

      reply	other threads:[~2006-03-11 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 19:11 [Qemu-devel] [PATCH] Add more devices for MIPS system emulation Thiemo Seufer
2006-02-22 15:28 ` Paul Brook
2006-02-22 17:35   ` Thiemo Seufer
2006-02-23 19:24     ` Paul Brook
2006-02-23 21:37       ` Thiemo Seufer
2006-02-23 21:44         ` Paul Brook
2006-03-06 14:50           ` Thiemo Seufer
2006-03-11 21:25             ` Paul Brook [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=200603112125.05107.paul@codesourcery.com \
    --to=paul@codesourcery.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).