qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: qemu-devel@nongnu.org
Cc: vineshp@xilinx.com, peter.maydell@linaro.org,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	john.williams@xilinx.com, pbonzini@redhat.com,
	edgar.iglesias@gmail.com
Subject: [Qemu-devel] [PATCH v2 0/6] QOMify pflash_cfi0x + PL353 for Xilinx Zynq
Date: Mon, 22 Oct 2012 17:18:58 +1000	[thread overview]
Message-ID: <cover.1350889929.git.peter.crosthwaite@xilinx.com> (raw)

This series adds the PL353 to Xilinx Zynq with both NAND and pflashes attached. Had to QOMify the pflash_cfi0x devices to get them working with PL35x in the least hackish way. Regression tested pflash_cfi_01 using petalogix-ml605 and pflash_cfi_02 tested using zynq. Further testing by clients of the pflash would be appreciated.

The pl35x is setup as a generalisation of all the pl35x family (i.e. it implements all of PL351-pl354). Once we get to actually implementing some of the register ops of this SRAM interface we could add this to vexpress for its PL354. The PL35x is incomplete (see the FIXME:s) at the moment but im pushing for this now as the more conterversial QOM-entangled aspects of this device model are encapsulated by this series. The device does also fully work for Linux.

Changlog:
Changed from v1:
Address PMM and Paolos Reviews (P3).
Fixed a compile error in in pflash when debug was turned on (P6)
Removed NAND READ_STATUS address reset patch (fomerly P6)

Peter Crosthwaite (6):
  pflash_cfi0x: remove unused base field
  pflash_cfi01: remove unused total_len field
  pflash_cfi0x: QOMified
  hw: Model of Primecell pl35x mem controller
  xilinx_zynq: add pl353
  pflash_cfi01: Fix debug mode printfery

 default-configs/arm-softmmu.mak |    1 +
 hw/Makefile.objs                |    1 +
 hw/pflash_cfi01.c               |  149 ++++++++++++++------
 hw/pflash_cfi02.c               |  162 +++++++++++++++------
 hw/pl35x.c                      |  299 +++++++++++++++++++++++++++++++++++++++
 hw/xilinx_zynq.c                |   50 ++++++-
 6 files changed, 560 insertions(+), 102 deletions(-)
 create mode 100644 hw/pl35x.c

             reply	other threads:[~2012-10-22  7:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  7:18 Peter Crosthwaite [this message]
2012-10-22  7:18 ` [Qemu-devel] [PATCH v2 1/6] pflash_cfi0x: remove unused base field Peter Crosthwaite
2012-10-22  7:19 ` [Qemu-devel] [PATCH v2 2/6] pflash_cfi01: remove unused total_len field Peter Crosthwaite
2012-10-22  7:19 ` [Qemu-devel] [PATCH v2 3/6] pflash_cfi0x: QOMified Peter Crosthwaite
2012-10-22 14:36   ` Peter Maydell
2012-10-22  7:19 ` [Qemu-devel] [PATCH v2 4/6] hw: Model of Primecell pl35x mem controller Peter Crosthwaite
2012-10-22 16:12   ` Peter Maydell
2012-10-22 18:43     ` Peter Crosthwaite
2012-10-22  7:19 ` [Qemu-devel] [PATCH v2 5/6] xilinx_zynq: add pl353 Peter Crosthwaite
2012-10-22 19:06   ` Peter Maydell
2013-11-06 12:46     ` vbalaji
2012-10-22  7:19 ` [Qemu-devel] [PATCH v2 6/6] pflash_cfi01: Fix debug mode printfery Peter Crosthwaite
2012-10-22 16:17   ` Peter Maydell

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=cover.1350889929.git.peter.crosthwaite@xilinx.com \
    --to=peter.crosthwaite@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@xilinx.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vineshp@xilinx.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).