qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: victortoso@redhat.com, berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: Half a usb-redir idea
Date: Wed, 17 Mar 2021 09:10:51 +0000	[thread overview]
Message-ID: <YFHHm8CWwUUc2B7o@work-vm> (raw)
In-Reply-To: <20210317062404.bkl5s4qmtaeg2yeo@sirius.home.kraxel.org>

* Gerd Hoffmann (kraxel@redhat.com) wrote:
> On Tue, Mar 16, 2021 at 05:21:02PM +0000, Dr. David Alan Gilbert wrote:
> > Hi,
> >   I've got a half-baked idea, which I thought might be worth mentioning.
> > 
> > How hard would it be to give qemu a usbredir server rather than client?
> 
> The usb part is probably not that hard.  The devices are not standalone
> though.  Tricky is the integration with the rest of qemu, with the input
> subsystem (hid devices), chardevs (usb-serial), network (usb-net), sound
> (usb-audio), block (usb-storage), ...

As long as this was still the qemu binary would that be a problem?

> ccid and u2f are probably easierst.
> mtp should not be hard too.
> maybe storage when limiting support to storage daemon.
> then it'll be tricky.
> maybe the multi-process qemu effort solves (some of) these problems.

It doesn't handle remote does it?

Dave

> take care,
>   Gerd
> 
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2021-03-17  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 17:21 Half a usb-redir idea Dr. David Alan Gilbert
2021-03-16 18:40 ` Philippe Mathieu-Daudé
2021-03-16 18:44   ` Dr. David Alan Gilbert
2021-03-16 21:06     ` Marc-André Lureau
2021-03-17  6:30     ` Gerd Hoffmann
2021-03-17  6:24 ` Gerd Hoffmann
2021-03-17  9:10   ` Dr. David Alan Gilbert [this message]
2021-03-17 10:16     ` Gerd Hoffmann
2021-03-17 10:41       ` Thanos Makatos

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=YFHHm8CWwUUc2B7o@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=victortoso@redhat.com \
    /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).