From: Greg KH <greg@kroah.com>
To: Jeremy White <jwhite@codeweavers.com>
Cc: Alex Elsayed <eternaleye@gmail.com>,
linux-usb@vger.kernel.org, spice-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] Add a usbredir kernel module to remotely connect USB devices over IP.
Date: Wed, 22 Jul 2015 07:34:03 -0700 [thread overview]
Message-ID: <20150722143403.GA3475@kroah.com> (raw)
In-Reply-To: <55AFA2C9.9010702@codeweavers.com>
On Wed, Jul 22, 2015 at 09:03:53AM -0500, Jeremy White wrote:
> On 07/09/2015 05:06 AM, Alex Elsayed wrote:
> >Alan Stern wrote:
> >
> >>On Mon, 6 Jul 2015, Jeremy White wrote:
> >>
> >>>Anything else fundamental to usbip that should inform the design of a
> >>>usbredir driver? usbip appears to be based off a 2004 vintage of
> >>>dummy_hcd. I'll look thoughtfully at the current dummy_hcd; please let
> >>>me know if there is anything else I should consider.
> >>
> >>One thing that springs to mind is USB-3 streams. When dummy-hcd was
> >>expanded to include USB-3, that was the major new ingredient.
> >
> >Another thing that comes to mind is that the USB-IF has its own official
> >standard for this kind of thing now, called Media-Agnostic USB[1]. In
> >November of 2014 a driver[2] was posted, followed by a second version[3],
> >and it is apparently being refined inside Intel[4].
> >
> >[1]
> >http://www.usb.org/developers/docs/devclass_docs/Media_Agnostic_USB_v1.0.zip
> >[2] http://thread.gmane.org/gmane.linux.kernel/1820297
> >[3] http://thread.gmane.org/gmane.linux.drivers.driver-project.devel/60498
> >[4] http://article.gmane.org/gmane.linux.drivers.driver-project.devel/60757
>
> Thanks for the pointer, Alex.
>
> I spent some time with the spec and their proposed code. It does seem
> plausible that XSpice could use a mausb/usbredir protocol converter. So if
> there was a mausb kernel module, I could potentially implement support in
> XSpice in user space and not need a usbredir module.
>
> I sent an email to the two developers at Intel to ask if there had been any
> further progress and if I could collaborate with them. I have not heard
> back.
>
> The MA spec is substantial and seems well thought out. But the usbredir
> protocol has the virtue of being relatively mature - it's 5 years old, with
> code in daily use.
>
> At this point it seems the best path forward is to continue work on the
> usbredir kernel module, which I will do unless I get some new information.
Please work with the existing people, or with the existing spec, I don't
want to be adding multiple versions of this type of protocol to the
kernel. As it is, I really don't even want to take your code, given
that usbip is already there. Ignoring it isn't ok.
thanks,
greg k-h
next prev parent reply other threads:[~2015-07-22 14:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:44 [RFC PATCH 0/1] RFC - Implement a usbredir kernel module Jeremy White
2015-06-30 21:44 ` [RFC PATCH 1/1] Add a usbredir kernel module to remotely connect USB devices over IP Jeremy White
2015-06-30 23:48 ` Greg KH
2015-07-01 3:34 ` Jeremy White
2015-07-01 5:44 ` Greg KH
2015-07-01 15:55 ` Jeremy White
2015-07-01 16:13 ` Greg KH
2015-07-01 18:39 ` Hans de Goede
2015-07-07 16:47 ` Jeremy White
2015-07-08 7:11 ` Hans de Goede
2015-07-09 0:19 ` Jeremy White
2015-07-01 9:06 ` [Spice-devel] " Daniel P. Berrange
2015-07-01 18:31 ` Jeremy White
2015-07-01 18:45 ` Hans de Goede
2015-07-02 8:45 ` Oliver Neukum
2015-07-02 11:35 ` Hans de Goede
2015-07-02 12:10 ` Oliver Neukum
2015-07-02 15:57 ` Jeremy White
2015-07-02 18:46 ` Oliver Neukum
2015-07-02 19:02 ` Jeremy White
2015-07-02 19:59 ` Alan Stern
2015-07-02 20:06 ` Jeremy White
2015-07-02 20:20 ` Alan Stern
2015-07-03 8:51 ` Krzysztof Opasiak
2015-07-03 14:04 ` Alan Stern
2015-07-06 8:20 ` Oliver Neukum
2015-07-06 20:14 ` Jeremy White
2015-07-06 20:22 ` Alan Stern
[not found] ` <mnlh2b$1cs$1@ger.gmane.org>
2015-07-22 14:03 ` Jeremy White
2015-07-22 14:34 ` Greg KH [this message]
2015-07-22 16:55 ` Jeremy White
2015-07-22 17:59 ` Sean O. Stalley
2015-07-23 0:20 ` Jeremy White
2015-12-09 22:32 ` Jeremy White
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=20150722143403.GA3475@kroah.com \
--to=greg@kroah.com \
--cc=eternaleye@gmail.com \
--cc=jwhite@codeweavers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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