From: Clement Deschamps <1772165@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1772165] Re: arm raspi2/raspi3 emulation has no USB support
Date: Mon, 19 Aug 2019 14:47:29 -0000 [thread overview]
Message-ID: <156622604957.26089.6280022026050715916.malone@soybean.canonical.com> (raw)
In-Reply-To: 152673688616.9061.7617411809661975686.malonedeb@chaenomeles.canonical.com
It looks like a similar USB controller is part of a TI SoC:
http://www.ti.com/lit/ug/spruhj7a/spruhj7a.pdf
Clement
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1772165
Title:
arm raspi2/raspi3 emulation has no USB support
Status in QEMU:
Confirmed
Bug description:
Using Qemu 2.12.0 on ArchLinux.
Trying to emulate arm device with `qemu-system-arm` and attach usb
device for unput using
` -usb -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002 `
# lsusb returns
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 014: ID 13d3:3487 IMC Networks
Bus 001 Device 004: ID 0457:11af Silicon Integrated Systems Corp.
Bus 001 Device 003: ID 0bda:57e6 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# qemu returns
qemu-system-arm: -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002: Bus '001' not found
Tried with connecting external usb keyboard but that didn't seem to work either.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1772165/+subscriptions
next prev parent reply other threads:[~2019-08-19 15:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 13:34 [Qemu-devel] [Bug 1772165] [NEW] qemu-system-arm: -device usb-host, bus=001, vendorid=0x04f2, productid=0x0111: Bus '001' not found George
2018-05-19 13:43 ` [Qemu-devel] [Bug 1772165] " Peter Maydell
2018-05-19 13:53 ` George
2018-05-19 16:15 ` Peter Maydell
2018-05-19 17:04 ` George
2018-05-19 17:49 ` Peter Maydell
2018-05-19 19:07 ` George
2018-05-19 19:33 ` Peter Maydell
2018-05-19 19:58 ` George
2018-05-22 7:43 ` Gerd Hoffmann
2018-06-01 16:05 ` Peter Maydell
2018-07-06 13:10 ` [Qemu-devel] [Bug 1772165] Re: arm raspi2/raspi3 emulation has no USB support Peter Maydell
2019-07-22 20:19 ` Aditya Govardhan
2019-07-23 8:52 ` Peter Maydell
2019-08-19 2:56 ` Weber Kai via Qemu-devel
2019-08-19 9:16 ` Peter Maydell
2019-08-19 12:44 ` Clement Deschamps
2019-08-19 14:47 ` Clement Deschamps [this message]
2019-08-20 12:59 ` Davide Bacilieri
2020-05-16 15:35 ` Doug Rabson
2020-05-17 20:36 ` Paul Zimmerman
2020-10-05 15:10 ` Dims
2020-10-05 20:11 ` mcandre
2020-10-06 10:35 ` Peter Maydell
2020-10-06 10:35 ` Peter Maydell
2020-10-05 21:46 ` Paul Zimmerman
2020-10-05 22:10 ` Paul Zimmerman
2020-10-06 7:36 ` Dims
2020-10-06 7:38 ` Dims
2020-10-06 8:27 ` Paul Zimmerman
2020-10-06 8:34 ` Paul Zimmerman
2020-11-17 9:47 ` Thomas Huth
2022-02-22 13:56 ` Carlo Bramini
2022-09-18 11:07 ` Philippe Mathieu-Daudé via
2022-09-18 11:07 ` Philippe Mathieu-Daudé
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=156622604957.26089.6280022026050715916.malone@soybean.canonical.com \
--to=1772165@bugs.launchpad.net \
--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).