From: Dirk Behme <dirk.behme@googlemail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add MIPS ELF loader
Date: Thu, 30 Mar 2006 15:40:25 +0200 [thread overview]
Message-ID: <442BDFC9.40009@gmail.com> (raw)
In-Reply-To: <20060328130159.GA31939@networkno.de>
Thiemo Seufer wrote:
> On Tue, Mar 28, 2006 at 08:57:15AM +0200, Dirk Behme wrote:
>>What about the patch in attachment? It first tries to load
>>image as an ELF file. If this fails it falls back to raw
>>image load. Additionally, it takes feature of patch above to
>>go on even if no BIOS is found.
>
>
> A slightly more polished version with less noisy messages is appended.
> It also adjusts the ramdisk load address to physical addressing,
> similiar to the binary kernel load.
One question I just found:
If we go on if no BIOS is found/executed and we load some
stuff to e.g. 0x80010000, where is the default address
translation made? As I understand MIPS, code in kseg0
(0x80000000) and kseg1 (0xA0000000) should be executable
without MMU/TLB setup because it is mapped by default to
physical 0x0. But looks to me that I get a
cpu_mips_handle_mmu_fault pc 80010000 ad 80010000 rw 2
is_user 0 smmu 1
for it.
Dirk
next prev parent reply other threads:[~2006-03-30 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 6:57 [Qemu-devel] [PATCH] Add MIPS ELF loader Dirk Behme
2006-03-28 13:01 ` Thiemo Seufer
2006-03-30 13:40 ` Dirk Behme [this message]
2006-03-30 13:53 ` Thiemo Seufer
2006-03-30 14:29 ` Alexander Voropay
2006-03-30 17:34 ` Dirk Behme
[not found] ` <442C0F57.3010200@gmail.com>
2006-04-02 12:54 ` Alexander Voropay
2006-04-23 17:16 ` Fabrice Bellard
2006-04-25 23:57 ` Thiemo Seufer
[not found] <154e01c66453$111e4f20$e90d11ac@spb.in.rosprint.ru>
2006-04-20 10:16 ` Marius Groeger
2006-04-20 10:28 ` Thiemo Seufer
2006-04-20 11:02 ` Alexander Voropay
2006-04-20 12:19 ` Alexander Voropay
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=442BDFC9.40009@gmail.com \
--to=dirk.behme@googlemail.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).