From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, jamie@shareable.org
Subject: Re: [Qemu-devel] Firewire/IEEE1394 OHCI for QEMU
Date: Sun, 12 Apr 2009 14:22:41 -0600 (MDT) [thread overview]
Message-ID: <20090412.142241.353385189.imp@bsdimp.com> (raw)
In-Reply-To: <20090412184718.GD4394@shareable.org>
In message: <20090412184718.GD4394@shareable.org>
Jamie Lokier <jamie@shareable.org> writes:
: Peter McCormick wrote:
: > At the moment I am still very early on in the implementation, not even
: > DMA contexts for async/iso are functional yet. But I have been inching
: > along getting Windows XP and Linux guests to recognize the presence of
: > an OHCI device.
:
: Is this the same OHCI which is used for USB? If so, it is useful to
: share any of the code from the existing UHCI and EHCI USB emulation,
: and also is it useful to think about attaching to USB devices (as well
: as Fireware) from your OHCI emulation?
No. It is just the same name.
Warner
next prev parent reply other threads:[~2009-04-12 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 21:50 [Qemu-devel] Firewire/IEEE1394 OHCI for QEMU Peter McCormick
2009-04-12 18:47 ` Jamie Lokier
2009-04-12 20:22 ` M. Warner Losh [this message]
2009-04-13 13:45 ` [Qemu-devel] " Julian Stecklina
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=20090412.142241.353385189.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=jamie@shareable.org \
--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 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).