All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-moxie: Use new qemu_ld/st opcodes
Date: Sat, 14 Dec 2013 23:18:37 -0500	[thread overview]
Message-ID: <871u1en3vm.fsf@moxielogic.com> (raw)
In-Reply-To: <1386780311-5612-1-git-send-email-rth@twiddle.net> (Richard Henderson's message of "Wed, 11 Dec 2013 08:45:11 -0800")

Richard Henderson <rth@twiddle.net> writes:

> Strict search-and-replace, since the moxie port does nothing complicated.
>
> Cc: Anthony Green <green@moxielogic.com>
> Signed-off-by: Richard Henderson <rth@twiddle.net>
> ---
>  target-moxie/translate.c | 52 ++++++++++++++++++++++++------------------------
>  1 file changed, 26 insertions(+), 26 deletions(-)
>
> Untested, since there's no openrisc images at http://wiki.qemu.org/Testing,
> but it's certainly a simple enough change.

Thanks Richard.  I've tested this patch and it's fine.

I don't have any disk images to post yet.  However, I do have some
firmware.  It's only about 5k, and normally lives in the FPGA hosting
Moxie, but it's useful as a quick test for qemu as well...

$ cat ./hello.srec | ./moxie-softmmu/qemu-system-moxie --nographic --machine marin --kernel ./bootrom.elf 
MOXIE On-Chip Bootloader v2.0
Copyright (c) 2013 Anthony Green <green@moxielogic.com>

Waiting for an S-Record Download or Remote GDB Connection...
Jumping to code at 0x30000000.
Hello World!

I see that the QEMU repo includes some firmware already.  Should I
submit this one as well?

Thanks,

AG

  reply	other threads:[~2013-12-15  4:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 16:45 [Qemu-devel] [PATCH] target-moxie: Use new qemu_ld/st opcodes Richard Henderson
2013-12-15  4:18 ` Anthony Green [this message]
2013-12-15  4:33   ` Peter Crosthwaite
2013-12-15 12:01 ` Anthony Green

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=871u1en3vm.fsf@moxielogic.com \
    --to=green@moxielogic.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.