From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9pi on qemu failure
Date: Sun, 8 Jun 2014 07:56:18 -0400 [thread overview]
Message-ID: <9c7f562d2d70f5c374f0a2b991a26545@brasstown.quanstro.net> (raw)
In-Reply-To: <C29BC174-DBDD-42D9-80FE-400C00963341@fb.com>
On Sat Jun 7 20:58:54 EDT 2014, pad@fb.com wrote:
> Hi,
>
> I've tried to run 9pi from richard miller on qemu but failed
> http://plan9.bell-labs.com/sources/contrib/miller/
>
> qemu-system-arm -cpu arm1176 -m 512 -M versatilepb -kernel 9pi
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x80010028
does anyone have the s9pi kernel image that corresponds to this?
i don't so i can't connect this failure to the source.
- erik
next prev parent reply other threads:[~2014-06-08 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 0:57 Yoann Padioleau
2014-06-08 11:56 ` erik quanstrom [this message]
2014-06-08 16:02 [9fans] Fwd: " Richard Miller
2014-06-09 7:40 ` [9fans] " Yoann Padioleau
2014-06-09 8:30 ` Skip Tavakkolian
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=9c7f562d2d70f5c374f0a2b991a26545@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).