From: itamar.tal4@gmail.com
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, ariel@guardicore.com, afaerber@suse.de,
Itamar Tal <itamar@guardicore.com>
Subject: [Qemu-devel] [PATCH v2] add 1394 bus support
Date: Sun, 19 Apr 2015 13:52:20 +0300 [thread overview]
Message-ID: <1429440741-48575-1-git-send-email-itamar@guardicore.com> (raw)
From: Itamar Tal <itamar@guardicore.com>
This patch add 1394 (firewire) support to x86_64 and i386 qemu
softmmu. It allows one virtual machine to be the server side and the
other to be the client side, connected by TCP stream socket (same
thing is possible using serial port). This is very useful in for
allowing legacy devices to communicate over the firewire channel, but
doesn't support USB communication. Especially, it's useful for remote
Windows kernel debugging over qemu for malware analysis and so on...
The patch was tested on major stable version 2.0.0, 2.2.1 and current
master (2.3.0rc?).
Itamar Tal (1):
add 1394 bus support
default-configs/i386-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
hw/1394/Makefile.objs | 1 +
hw/1394/hcd-ohci.c | 1754 ++++++++++++++++++++++++++++++++++++
hw/1394/hcd-ohci.h | 147 +++
hw/Makefile.objs | 1 +
6 files changed, 1905 insertions(+)
create mode 100644 hw/1394/Makefile.objs
create mode 100644 hw/1394/hcd-ohci.c
create mode 100644 hw/1394/hcd-ohci.h
--
2.3.4
next reply other threads:[~2015-04-19 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 10:52 itamar.tal4 [this message]
2015-04-19 10:52 ` [Qemu-devel] [PATCH v02] add 1394 bus support itamar.tal4
2015-04-19 15:47 ` Andreas Färber
2015-04-19 16:38 ` Itamar Tal
2015-04-19 17:21 ` Andreas Färber
2015-04-20 11:59 ` Itamar Tal
2015-04-19 20:15 ` 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=1429440741-48575-1-git-send-email-itamar@guardicore.com \
--to=itamar.tal4@gmail.com \
--cc=afaerber@suse.de \
--cc=ariel@guardicore.com \
--cc=itamar@guardicore.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).