From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Max Krasnyansky <maxk@kernel.org>, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 5/5] husb: rewrite Linux host USB layer, fully async operation
Date: Fri, 15 Aug 2008 20:53:26 +0100 [thread overview]
Message-ID: <200808152053.27587.paul@codesourcery.com> (raw)
In-Reply-To: <48A5D32E.2030208@kernel.org>
> Given that OHCI is much more complex than UHCI (both the code and the spec)
> I decided to give up on OHCI, at least for now. I noticed Codesourcery
> copyright on OHCI. Did you have anything to do with the OHCI implementation?
Yes, I wrote the current OHCI support, based on some initial patches by
Gianni.
I found OHCI to be much easier to deal with than than UHCI. The low-level bits
of the USB protocol are fairly nasty. UHCI is a cheap and nasty host
solution, which directly exposes (and requires faking of) all the nasty low
level details and timing.
OHCI is a higher level interface which I found makes it much easier to
actually implement things sanely in a virtual environment.
> So we'd definitely need to work on OHCI if it's important for some
> platforms.
I consider OHCI to be important. x86 is abut the only target foolish enough to
use UHCI.
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, Max Krasnyansky <maxk@kernel.org>
Subject: Re: [Qemu-devel] [PATCH 5/5] husb: rewrite Linux host USB layer, fully async operation
Date: Fri, 15 Aug 2008 20:53:26 +0100 [thread overview]
Message-ID: <200808152053.27587.paul@codesourcery.com> (raw)
In-Reply-To: <48A5D32E.2030208@kernel.org>
> Given that OHCI is much more complex than UHCI (both the code and the spec)
> I decided to give up on OHCI, at least for now. I noticed Codesourcery
> copyright on OHCI. Did you have anything to do with the OHCI implementation?
Yes, I wrote the current OHCI support, based on some initial patches by
Gianni.
I found OHCI to be much easier to deal with than than UHCI. The low-level bits
of the USB protocol are fairly nasty. UHCI is a cheap and nasty host
solution, which directly exposes (and requires faking of) all the nasty low
level details and timing.
OHCI is a higher level interface which I found makes it much easier to
actually implement things sanely in a virtual environment.
> So we'd definitely need to work on OHCI if it's important for some
> platforms.
I consider OHCI to be important. x86 is abut the only target foolish enough to
use UHCI.
Paul
next prev parent reply other threads:[~2008-08-15 19:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 4:22 [PATCH 0/5] Various USB fixes and improvements Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 4:22 ` [PATCH 1/5] husb: support for USB host device auto disconnect Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 16:28 ` Anthony Liguori
2008-08-14 16:28 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:26 ` Max Krasnyansky
2008-08-14 19:26 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 21:41 ` Max Krasnyansky
2008-08-14 21:41 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 4:22 ` [PATCH 2/5] husb: support for USB host device auto connect Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 16:41 ` Anthony Liguori
2008-08-14 16:41 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:38 ` Max Krasnyansky
2008-08-14 19:38 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 20:21 ` Anthony Liguori
2008-08-14 20:21 ` [Qemu-devel] " Anthony Liguori
2008-08-14 20:34 ` Max Krasnyansky
2008-08-14 20:34 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 20:41 ` Anthony Liguori
2008-08-14 20:41 ` [Qemu-devel] " Anthony Liguori
2008-08-14 21:14 ` François Revol
2008-08-15 7:46 ` Guido Günther
2008-08-15 7:46 ` Guido Günther
2008-08-15 18:24 ` Max Krasnyansky
2008-08-15 18:31 ` Javier Guerra
2008-08-18 18:21 ` Max Krasnyansky
2008-08-18 18:52 ` Javier Guerra
2008-08-18 18:56 ` Jamie Lokier
2008-08-18 18:56 ` Jamie Lokier
2008-08-17 7:52 ` Avi Kivity
2008-08-18 18:46 ` Max Krasnyansky
2008-08-18 14:11 ` Anthony Liguori
2008-08-18 18:16 ` Max Krasnyansky
2008-08-14 4:22 ` [PATCH 3/5] usb: generic packet handler cleanup and documentation Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 4:22 ` [PATCH 4/5] uhci: rewrite UHCI emulator, fully async operation with multiple outstanding transactions Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-14 17:51 ` Anthony Liguori
2008-08-14 17:51 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:49 ` Max Krasnyansky
2008-08-14 19:49 ` [Qemu-devel] " Max Krasnyansky
2008-10-11 23:54 ` [Qemu-devel] " Juergen Lock
2008-10-15 19:54 ` Max Krasnyansky
2008-10-15 22:05 ` andrzej zaborowski
2008-10-16 21:25 ` Juergen Lock
2008-08-14 4:22 ` [PATCH 5/5] husb: rewrite Linux host USB layer, fully async operation Max Krasnyansky
2008-08-14 4:22 ` [Qemu-devel] " Max Krasnyansky
2008-08-15 14:24 ` Paul Brook
2008-08-15 14:24 ` Paul Brook
2008-08-15 19:04 ` Max Krasnyansky
2008-08-15 19:53 ` Paul Brook [this message]
2008-08-15 19:53 ` Paul Brook
2008-08-18 18:40 ` Max Krasnyansky
2008-08-14 17:55 ` [PATCH 0/5] Various USB fixes and improvements Anthony Liguori
2008-08-14 17:55 ` [Qemu-devel] " Anthony Liguori
2008-08-14 19:55 ` Max Krasnyansky
2008-08-14 19:55 ` [Qemu-devel] " Max Krasnyansky
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=200808152053.27587.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=kvm@vger.kernel.org \
--cc=maxk@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.