From: Anthony Liguori <aliguori@us.ibm.com>
To: Michael Walle <michael@walle.cc>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] lm32 fixes and new milkymist hardware support
Date: Thu, 29 Sep 2011 13:27:35 -0500 [thread overview]
Message-ID: <4E84B897.6060605@us.ibm.com> (raw)
In-Reply-To: <1316127541-9015-1-git-send-email-michael@walle.cc>
On 09/15/2011 05:58 PM, Michael Walle wrote:
> Hi Anthony,
>
> here is a patch for target-lm32, which is broken with the current master.
>
> Additionally, support for the new uart of the milkymist SoC is added.
>
>
> The following changes since commit ef4f97cba2a354656b00eb8659bf61ab2321fa4e:
>
> Merge remote-tracking branch 'qemu-kvm-tmp/memory/core' into staging (2011-09-15 13:33:03 -0500)
>
> are available in the git repository at:
>
> http://git.serverraum.org/git/mw/qemu-lm32.git for-upstream
Please publish a git URI. Fetching over HTTP is painful, particularly when the
connection to the server isn't very good.
Regards,
Anthony Liguori
>
> Michael Walle (3):
> lm32: add missing qemu_init_vcpu() call
> milkymist_uart: support new core version
> milkymist: new interrupt map
>
> hw/milkymist-hw.h | 5 +--
> hw/milkymist-uart.c | 72 +++++++++++++++++++++++++++++++++++++++++++------
> hw/milkymist.c | 14 +++++-----
> target-lm32/helper.c | 1 +
> trace-events | 4 +-
> 5 files changed, 75 insertions(+), 21 deletions(-)
>
>
next prev parent reply other threads:[~2011-09-29 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 22:58 [Qemu-devel] [PULL] lm32 fixes and new milkymist hardware support Michael Walle
2011-09-15 22:58 ` [Qemu-devel] [PATCH 1/3] lm32: add missing qemu_init_vcpu() call Michael Walle
2011-09-15 22:59 ` [Qemu-devel] [PATCH 2/3] milkymist_uart: support new core version Michael Walle
2011-09-15 22:59 ` [Qemu-devel] [PATCH 3/3] milkymist: new interrupt map Michael Walle
2011-09-29 18:27 ` Anthony Liguori [this message]
2011-10-03 13:36 ` [Qemu-devel] [PULL] lm32 fixes and new milkymist hardware support Michael Walle
2011-10-08 16:36 ` Blue Swirl
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=4E84B897.6060605@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=michael@walle.cc \
--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 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.