From: "Emilio G. Cota" <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>, Stafford Horne <shorne@gmail.com>
Subject: [Qemu-devel] [PATCH 0/2] target/openrisc: translator loop conversion
Date: Sat, 17 Feb 2018 20:32:35 -0500 [thread overview]
Message-ID: <1518917557-12063-1-git-send-email-cota@braap.org> (raw)
Tested on the image linked from the wiki:
https://wiki.qemu.org/Testing/System_Images
Boot after decompressing with:
or1k-softmmu/qemu-system-or1k -cpu or1200 -M or1k-sim \
-kernel path/to/or1k-linux-4.10 \
-serial stdio -nographic -monitor none
Thanks,
Emilio
next reply other threads:[~2018-02-18 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 1:32 Emilio G. Cota [this message]
2018-02-18 1:32 ` [Qemu-devel] [PATCH 1/2] target/openrisc: convert to DisasContextBase Emilio G. Cota
2018-02-18 3:10 ` Stafford Horne
2018-02-18 6:11 ` Emilio G. Cota
2018-02-21 18:22 ` Richard Henderson
2018-02-18 1:32 ` [Qemu-devel] [PATCH 2/2] target/openrisc: convert to TranslatorOps Emilio G. Cota
2018-02-18 3:13 ` Stafford Horne
2018-02-21 18:24 ` Richard Henderson
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=1518917557-12063-1-git-send-email-cota@braap.org \
--to=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=shorne@gmail.com \
/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).