qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Alexander Graf <agraf@suse.de>,
	Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH 00/17 v3] LatticeMico32 target
Date: Thu, 17 Feb 2011 23:45:01 +0100	[thread overview]
Message-ID: <1297982718-21865-1-git-send-email-michael@walle.cc> (raw)

This patchset adds support for the LatticeMico32 softcore processor by
Lattice Semiconductor.

Changes since v2:
 - lots of CODING_STYLE fixes
 - reworked pic and juart model, CPUState is not passed anymore
 - use qdev reset field instead of qemu_register_reset()
 - add missing include guards
 - merged lm32_pic_cpu.c into boards file
 - removed buggy qemu_irq_lower() in reset functions
 - converted hw_error to error_report()

Changes since v1:
 - removed variables which are no longer in use
 - replaced some tcg ops with specialized ones
 - kill VM in case of an unknown opcode
 - fixed tracepoints format strings to match existing ones

             reply	other threads:[~2011-02-17 22:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 22:45 Michael Walle [this message]
2011-02-17 22:45 ` [Qemu-devel] [PATCH 01/17] LatticeMico32 target support Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 02/17] lm32: translation routines Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 03/17] lm32: translation code helper Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 04/17] lm32: machine state loading/saving Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 05/17] lm32: gdbstub support Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 06/17] lm32: interrupt controller model Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 07/17] lm32: juart model Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 08/17] lm32: pic and juart helper functions Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 09/17] lm32: timer model Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 10/17] lm32: uart model Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 11/17] lm32: system control model Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 12/17] lm32: support for creating device tree Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 13/17] lm32: EVR32 and uclinux BSP Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 14/17] lm32: todo and documentation Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 15/17] lm32: opcode testsuite Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 16/17] Add lm32 target to configure Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 17/17] MAINTAINERS: add LatticeMico32 maintainer Michael Walle
2011-02-24 23:03 ` [Qemu-devel] [PATCH 00/17 v3] LatticeMico32 target Michael Walle
2011-03-01 21:31   ` Edgar E. Iglesias
2011-03-05  9:55     ` Blue Swirl
2011-03-06 22:47     ` Michael Walle
2011-03-07 13:20       ` Edgar E. Iglesias
2011-03-13 22:36         ` Michael Walle

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=1297982718-21865-1-git-send-email-michael@walle.cc \
    --to=michael@walle.cc \
    --cc=agraf@suse.de \
    --cc=blauwirbel@gmail.com \
    --cc=edgar.iglesias@gmail.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 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).