From: Anthony Liguori <anthony@codemonkey.ws>
To: Attila Sukosd <attila.sukosd@gmail.com>
Cc: spice-devel@lists.freedesktop.org,
"Frédéric Grelot" <fredericg_99@yahoo.fr>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Spice-devel] [Qemu-devel] RFC: usb redirection over the network, interesting outside of spice?
Date: Mon, 29 Nov 2010 11:49:11 -0600 [thread overview]
Message-ID: <4CF3E797.7070401@codemonkey.ws> (raw)
In-Reply-To: <AANLkTin=69cy=s7DkeaM803GLWSF8trZ-j6tNYzgg_FN@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
On 11/29/2010 11:37 AM, Attila Sukosd wrote:
> Hi,
>
> I guess it should be abstract enough to support multiple back-ends, be
> it a kernel driver or through libusb?
Is this something that should just live in libusb?
If what libusb presented QEMU was actually implemented as USB-over-IP,
QEMU wouldn't know the difference at all. I think it would also be very
useful to be able for libusb-based applications to work with remote devices.
What is unclear to me is what role QEMU would play in setting up remove
USB-over-IP devices. Pushing it down to the libusb layer completely
takes QEMU out the picture which creates a clean separation layer.
There are emulated devices in QEMU which we create and control and then
there are passthrough devices that QEMU doesn't have any role in creating.
Regards,
Anthony Liguori
>
> Rgrds,
>
> Attila
>
>
> 2010/11/29 Gerd Hoffmann <kraxel@redhat.com <mailto:kraxel@redhat.com>>
>
> Hi,
>
>
> I'm note sure about what I will say, but will a kernel approach
> handle specific disconnection/reconnection of devices, that libusb
> cannot?
>
>
> Don't know, didn't investigate (yet) what libusb can do and what
> it can't.
>
> cheers,
> Gerd
>
>
>
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@lists.freedesktop.org
> <mailto:Spice-devel@lists.freedesktop.org>
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>
>
[-- Attachment #2: Type: text/html, Size: 2678 bytes --]
next prev parent reply other threads:[~2010-11-29 17:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101129101727.2B64E2B679@zimbra14-e2.priv.proxad.net>
2010-11-29 14:33 ` [Qemu-devel] RFC: usb redirection over the network, interesting outside of spice? François Revol
2010-11-29 15:47 ` Gerd Hoffmann
2010-11-29 15:10 ` [Spice-devel] " Frédéric Grelot
2010-11-29 16:35 ` Gerd Hoffmann
2010-11-29 17:37 ` Attila Sukosd
2010-11-29 17:49 ` Anthony Liguori [this message]
2010-11-29 18:07 ` Alexander Graf
2010-11-30 8:54 ` Gerd Hoffmann
2010-11-30 11:26 ` Hans de Goede
2010-11-30 11:32 ` Alon Levy
2010-11-30 12:23 ` Hans de Goede
2010-12-01 11:04 ` Paul Brook
2010-12-01 11:49 ` Hans de Goede
2010-12-01 12:12 ` Paul Brook
2010-11-29 16:05 ` François Revol
2010-12-01 13:34 ` [Libusb-devel] " Peter Stuge
2010-11-29 17:13 ` Paul Brook
2010-11-30 11:07 ` [Qemu-devel] Using usbip for usb network redirection (was RFC: usb redirection over the network, interesting outside of spice?) Hans de Goede
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=4CF3E797.7070401@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=attila.sukosd@gmail.com \
--cc=fredericg_99@yahoo.fr \
--cc=kraxel@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).