From: Richard Henderson <rth@twiddle.net>
To: Michael Rolnik <mrolnik@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Michael Rolnik <rolnik@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v4 4/9] target-avr: adding instructions encodings
Date: Wed, 8 Jun 2016 21:53:05 -0700 [thread overview]
Message-ID: <54a7af50-dc93-c5cf-8c08-d8712a8a0d56@twiddle.net> (raw)
In-Reply-To: <CAK4993jzfrnfuNVGkzxDgsr864RRiS90D2vFMm4CM3qmJRp04g@mail.gmail.com>
On 06/08/2016 02:15 PM, Michael Rolnik wrote:
> I can send the sources, of my generator if you want.
> However I have not time to make it a part of AVR patch right now.
> let's finish with AVR cores and then when I have time I will be happy to
> QEMUify the generator.
>
I think you should add the generator even if it's not (currently) run as part
of the normal build process.
Perhaps put the build commands you used in the target-avr/Makefile, commented out.
r~
next prev parent reply other threads:[~2016-06-09 4:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 10:37 [Qemu-devel] [PATCH v4 0/9] 8bit AVR cores Michael Rolnik
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 1/9] target-avr: AVR cores support is added. 1. basic CPU structure 2. registers 3. no instructions Michael Rolnik
2016-06-06 20:15 ` Richard Henderson
2016-06-07 6:32 ` Michael Rolnik
2016-06-07 14:28 ` Richard Henderson
2016-06-08 19:49 ` Michael Rolnik
2016-06-09 4:43 ` Richard Henderson
2016-06-06 22:27 ` Peter Maydell
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 2/9] target-avr: adding AVR CPU features/flavors Michael Rolnik
2016-06-06 20:25 ` Richard Henderson
2016-06-08 20:53 ` Michael Rolnik
2016-06-09 4:48 ` Richard Henderson
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 3/9] target-avr: adding a sample AVR board Michael Rolnik
2016-06-06 20:49 ` Richard Henderson
2016-06-06 21:55 ` Peter Maydell
2016-07-05 22:22 ` Michael Rolnik
2016-07-05 22:31 ` Peter Maydell
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 4/9] target-avr: adding instructions encodings Michael Rolnik
2016-06-06 21:38 ` Richard Henderson
2016-06-06 22:06 ` Peter Maydell
2016-06-08 21:15 ` Michael Rolnik
2016-06-09 4:53 ` Richard Henderson [this message]
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 5/9] target-avr: adding AVR interrupt handling Michael Rolnik
2016-06-06 21:44 ` Richard Henderson
2016-06-06 22:17 ` Peter Maydell
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 7/9] target-avr: adding instruction decoder Michael Rolnik
2016-06-06 22:06 ` Richard Henderson
2016-06-06 10:37 ` [Qemu-devel] [PATCH v4 8/9] target-avr: adding instruction translation Michael Rolnik
2016-06-06 23:05 ` Richard Henderson
2016-06-06 10:38 ` [Qemu-devel] [PATCH v4 9/9] target-avr: updating translate.c to use instructions translation Michael Rolnik
2016-06-06 19:40 ` [Qemu-devel] [PATCH v4 0/9] 8bit AVR cores Richard Henderson
2016-06-06 19:49 ` Michael Rolnik
2016-06-06 19:53 ` Michael Rolnik
2016-06-06 20:16 ` Richard Henderson
2016-06-06 20:21 ` Richard Henderson
[not found] ` <1465209480-71364-7-git-send-email-rolnik@amazon.com>
2016-06-06 21:58 ` [Qemu-devel] [PATCH v4 6/9] target-avr: adding helpers for IN, OUT, SLEEP, WBR & unsupported instructions 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=54a7af50-dc93-c5cf-8c08-d8712a8a0d56@twiddle.net \
--to=rth@twiddle.net \
--cc=mrolnik@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rolnik@amazon.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).