From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] USB over network
Date: Tue, 7 Oct 2008 21:08:05 +0300 [thread overview]
Message-ID: <f43fc5580810071108o58a2e660nbfbaf2f022cfb32d@mail.gmail.com> (raw)
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A2C9439E@EXVBE011-2.exch011.intermedia.net>
On 10/7/08, Gal Hammer <gal@qumranet.com> wrote:
> > How about USB drives or printers, do they work?
>
>
> Basically, if it works locally, it should work over network. The remote feature should be as good as the qemu's current support for USB emulation.
>
>
> > A few comments:
> > - 'static' can be applied to a lot of functions
>
>
> I'll search for these.
>
>
> > - instead of including linux/usb_ch9.h, you should define the
> > structures, like in usb-linux.c
>
>
> No problem.
>
>
> > - while the daemon is linux specific, the remote protocol looks like
> > host OS neutral, so it should not be too tightly tied to usb-linux.c
>
>
> The protocol is still in its pre-draft status.
I meant that also Windows and BSD clients could in theory use a USB
device from the Linux-only server, so the client end of the protocol
should be independent from usb-linux.c.
> > - name __ioctl looks like it could clash with system defines and it's
> > not very descriptive
>
>
> Will changed (Do you have an idea how to name it?).
USBRemoteIOCTLFunc?
> > - USB_REMOTE_MAGIC is not endian neutral, or is that the purpose?
>
>
> I didn't understand. Do you mean that the value might change if qemu is running on a different type of CPU?
Yes. That would cause problems if the server is different endian from
the client. In fact the whole protocol looks like it also assumes that
the server and client are same endian.
prev parent reply other threads:[~2008-10-07 18:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 11:43 [Qemu-devel] [PATCH] USB over network Gal Hammer
2008-10-06 12:09 ` Paul Brook
2008-10-06 12:22 ` Paul Brook
2008-10-06 12:42 ` Dor Laor
2008-10-06 13:15 ` Gal Hammer
2008-10-06 13:32 ` Paul Brook
2008-10-06 13:41 ` Anthony Liguori
2008-10-06 14:20 ` Gal Hammer
2008-10-06 15:24 ` Alexander Graf
2008-10-06 12:32 ` Daniel P. Berrange
2008-10-06 15:05 ` Blue Swirl
2008-10-07 8:34 ` Gal Hammer
2008-10-07 18:08 ` Blue Swirl [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=f43fc5580810071108o58a2e660nbfbaf2f022cfb32d@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).