From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: spice-devel@lists.freedesktop.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Spice-devel] RFC; usb redirection protocol
Date: Thu, 16 Dec 2010 09:15:13 +0100 [thread overview]
Message-ID: <4D09CA91.9020506@redhat.com> (raw)
In-Reply-To: <4D08B17E.90100@redhat.com>
Hi,
> It could be that the implementation decides to not handle synchroneous
> commands synchroneous at all. The main difference I'm trying to make
> here is between commands which do things to end points which cannot
> be done while other packets are in flight (like setting configuration,
> or interface alt setting) and commands (normal packets) of which there
> can be multiple in flight. I'm open to using a different term then
> synchroneous and async here.
Name them control / data packets?
cheers,
Gerd
prev parent reply other threads:[~2010-12-16 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:10 [Qemu-devel] RFC; usb redirection protocol Hans de Goede
2010-12-13 11:21 ` [Qemu-devel] Re: [Spice-devel] " Gerd Hoffmann
2010-12-15 12:15 ` Hans de Goede
2010-12-15 12:20 ` Frédéric Grelot
2010-12-18 16:30 ` Hans de Goede
2010-12-15 15:18 ` Alon Levy
2010-12-16 8:13 ` Gerd Hoffmann
2010-12-16 8:15 ` Gerd Hoffmann [this message]
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=4D09CA91.9020506@redhat.com \
--to=kraxel@redhat.com \
--cc=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.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).