From: Gerd Hoffmann <kraxel@redhat.com>
To: Natalia Portillo <claunia@claunia.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Ankit Verma <shiningankit@gmail.com>,
"Developers qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hi Natalia.. A query regarding QEMU
Date: Mon, 07 Nov 2011 12:28:13 +0100 [thread overview]
Message-ID: <4EB7C0CD.30402@redhat.com> (raw)
In-Reply-To: <70B51760-933C-4245-BDD9-26C404D75411@claunia.com>
Hi,
> What I can tell you is that Android phones/tablets are USB devices,
> and QEMU have an incomplete support for REAL USB devices with QEMU
> behaving as an USB host. But QEMU is not designed currently to work
> as a USB device to a real USB host.
>
> If you want to code that support yourself, you'll need a virtual host
> controller implementation on the host operating system, and then
> implementing QEMU behavior as an Android device (be it USB Mass
> Storage Device or Android Debug device).
Another option would be to explore the usbredir support recently added
to qemu. The focus of the current implementation is to support
forwarding usb devices over the network. You have a little server
running which export a usb device, and qemu's usbredir backend connects
to the server and allows the guest to access the device.
Of course you can replace the server side with something emulating a usb
device, for example a emulated android device with usb-host support,
i.e. you have two qemu's running, one with android, one with a linux or
windows guest os, and you'll link the two using the usbredir protocol.
Cc'ing Hans who wrote the usbredir support.
cheers,
Gerd
prev parent reply other threads:[~2011-11-07 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+A_OnXY5RU9iu_Gm4oTHGZmMwYKqWKgz+ZdS921wBQqeKa3BA@mail.gmail.com>
2011-11-04 3:55 ` [Qemu-devel] Hi Natalia.. A query regarding QEMU Natalia Portillo
2011-11-07 11:28 ` Gerd Hoffmann [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=4EB7C0CD.30402@redhat.com \
--to=kraxel@redhat.com \
--cc=claunia@claunia.com \
--cc=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shiningankit@gmail.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 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.