All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: spice-devel@lists.freedesktop.org,
	"François Revol" <revol@free.fr>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] RFC: usb redirection over the network, 	interesting outside of spice?
Date: Mon, 29 Nov 2010 17:13:22 +0000	[thread overview]
Message-ID: <201011291713.22233.paul@codesourcery.com> (raw)
In-Reply-To: <4CF3CB17.6000306@redhat.com>

>    Hi,
> 
> > Not me at the moment, but unless you tunnel it inside another
> > protocol, you'd really want to look at the existing USB-over-IP
> > protocols instead of reinventing the wheel:
> > http://usbip.sourceforge.net/ (some support in Linux already IIRC)
> > (and there are others which I don't recall)
> 
> Doesn't look very useful on a quick glance.
> 
> First: Yes, we wanna embed this into other protocol(s).
> 
> Second, seems usbip is implemented using special drivers in kernel space
> for both sides.  We will not need special drivers on the qemu side (we
> just hook up the devices to the emulated hci).  On the client side using
> libusb looks alot more sensible than requiring kernel modules.

I don't know how good the usp/ip stuff is, but I'd be very reluctant to invent 
yet annother remote-usb protocol.  USB is very hairy, so there's good reason 
to go with something that has already been tested.

IMO the ability to interact with the native kernel support is a feature in its 
own right.  If we end up with a libusb implementation of the usb/ip device 
end, then that only seems like a good thing - you potentialy get testing 
coverage from both qemu users and native vhci-hcd users.

Paul

  parent reply	other threads:[~2010-11-29 17:13 UTC|newest]

Thread overview: 20+ 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
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 [this message]
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
2010-11-29 10:11 [Qemu-devel] RFC: usb redirection over the network, interesting outside of spice? Hans de Goede
2010-11-29 11:50 ` Gerd Hoffmann

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=201011291713.22233.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    --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 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.