From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KmqL6-0006Yq-IB
	for qemu-devel@nongnu.org; Mon, 06 Oct 2008 09:41:32 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KmqL4-0006Xs-Si
	for qemu-devel@nongnu.org; Mon, 06 Oct 2008 09:41:32 -0400
Received: from [199.232.76.173] (port=51337 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KmqL4-0006Xm-I3
	for qemu-devel@nongnu.org; Mon, 06 Oct 2008 09:41:30 -0400
Received: from mail-gx0-f19.google.com ([209.85.217.19]:51129)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1KmqL4-0006uj-5I
	for qemu-devel@nongnu.org; Mon, 06 Oct 2008 09:41:30 -0400
Received: by gxk12 with SMTP id 12so5473882gxk.10
	for <qemu-devel@nongnu.org>; Mon, 06 Oct 2008 06:41:28 -0700 (PDT)
Message-ID: <48EA1585.90804@codemonkey.ws>
Date: Mon, 06 Oct 2008 08:41:25 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] USB over network
References: <ED2414DB5FBBCF4FA66ECE71F290E9A2B601E6@EXVBE011-2.exch011.intermedia.net>	<200810061309.10270.paul@codesourcery.com>
	<ED2414DB5FBBCF4FA66ECE71F290E9A2B601F5@EXVBE011-2.exch011.intermedia.net>
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A2B601F5@EXVBE011-2.exch011.intermedia.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Gal Hammer wrote:
>> Apart from anything else, it's missing documentation.
>>     
>
> I am aware of that. I'll document the work I've done so far and include
> the open issues that you (and others) wrote.
>  
>   
>> It looks like you have to start qemu with magic options on the remote
>> machine?
>>     
>
> No, qemu should be started with "-usbremote host:port" command line
> option. This will start a listener which wait for incoming remote
> connections. The remote connection is established with the qemu-usbd
> application. The qemu-usbd is executed on the local machine, the one
> that the USB device is attached to.
>   

I think it would be better to support a push instead of a pull model.  
For instance, something like:

-usbdevice remote:host:port

That connected to something that was listening on the machine that had 
the USB device.  If you really wanted a server, I'd suggest a syntax like:

-usbdevice remote:host:port,server

So at a high level, what's functional now, and how much work is needed 
to be completely functional?  Is there anything that isn't going to work 
because of fundamental issues?

Regards,

Anthony Liguori

> 	Gal.
>
>
>
>