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, kraxel@redhat.com,
edgar.iglesias@gmail.com, afaerber@suse.de
Subject: [Qemu-devel] [PATCH v3 0/8] Sysbus EHCI + Zynq USB.
Date: Mon, 29 Oct 2012 11:34:31 +1000 [thread overview]
Message-ID: <cover.1351473902.git.peter.crosthwaite@xilinx.com> (raw)
Added Sysbus variant of EHCI and attached it to Xilinx Zynq. The EHCI stuff is going to useful for Tegra too.
See http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg04100.html thread for the inital RFC discussion on this development.
Regession tested using i386 Debian (dd of=/dev/sdx ...) to get some test coverage outside of Zynq. More testing welcome.
Few other bits and pieces of cleanup in there too, around the EHCI_DEBUG printfery.
The series will rebase without conflict on the current pending usb patch queue (usb.68).
Changed since V2:
No more usages of unions, seperated out PCI and Sysbus structs and codepaths completely.
Removed init_ram hack for unimplemented EHCI regions.
Removed debug message cleanup patch (conflicts with pending USB [PULL] (usb.68))
Changed since V1:
Overhauled properties - moved them to class properties rather than object properties.
Various Review based fixes (Please see individual patch change logs)
Peter Crosthwaite (7):
usb/ehci: Use class_data to init PCI variations
usb/ehci: parameterise the register region offsets
usb/ehci: Abstract away PCI DMA API
usb/ehci: seperate out PCIisms
usb/ehci: Add Sysbus variant and Xilinx Zynq USB
xilinx_zynq: add USB controllers
usb/ehci: Guard definition of EHCI_DEBUG
Peter Maydell (1):
dma: Define dma_context_memory and use in sysbus-ohci
dma.h | 5 +
exec.c | 5 +
hw/usb/hcd-ehci.c | 339 +++++++++++++++++++++++++++++++++++------------------
hw/usb/hcd-ohci.c | 2 +-
hw/xilinx_zynq.c | 3 +
5 files changed, 238 insertions(+), 116 deletions(-)
next reply other threads:[~2012-10-29 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 1:34 Peter Crosthwaite [this message]
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 1/8] dma: Define dma_context_memory and use in sysbus-ohci Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 2/8] usb/ehci: Use class_data to init PCI variations Peter Crosthwaite
2012-10-29 9:35 ` Andreas Färber
2012-10-29 11:43 ` Peter Crosthwaite
2012-10-29 13:21 ` Andreas Färber
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 3/8] usb/ehci: parameterise the register region offsets Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 4/8] usb/ehci: Abstract away PCI DMA API Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 5/8] usb/ehci: seperate out PCIisms Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 6/8] usb/ehci: Add Sysbus variant and Xilinx Zynq USB Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 7/8] xilinx_zynq: add USB controllers Peter Crosthwaite
2012-10-29 1:34 ` [Qemu-devel] [PATCH v3 8/8] usb/ehci: Guard definition of EHCI_DEBUG Peter Crosthwaite
2012-10-29 7:48 ` [Qemu-devel] [PATCH v3 0/8] Sysbus EHCI + Zynq USB Gerd Hoffmann
2012-10-29 8:53 ` Andreas Färber
2012-10-29 9:41 ` Gerd Hoffmann
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.1351473902.git.peter.crosthwaite@xilinx.com \
--to=peter.crosthwaite@xilinx.com \
--cc=afaerber@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=john.williams@xilinx.com \
--cc=kraxel@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).