From: Gerd Hoffmann <kraxel@redhat.com>
To: walimis <walimisdev@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
peter.crosthwaite@xilinx.com,
Igor Mitsyanko <i.mitsyanko@samsung.com>,
qemu-devel@nongnu.org, andreas.faerber@web.de,
Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI
Date: Mon, 03 Dec 2012 14:37:48 +0100 [thread overview]
Message-ID: <50BCAB2C.6040106@redhat.com> (raw)
In-Reply-To: <20121203123821.GE6029@pek-lwang0-d1>
Hi,
>>> Qemu doesn't provide some properties, such as "bus", to specify which EHCI controller the
>>> usb device attach to. If we use "device" and "usb-storage", we never attach the usb
>>> device to the specified EHCI controller.
>>
>> -device certainly ought to let you specify a bus= property;
>
> Sorry, I don't know the bus= property.
> But why both EHCI controller are named "usb-bus.0"? How to distinguish the
> different usb usb?
That is the default name. For usb controllers added via -device the bus
name is derived from the device name, i.e. '-device usb-ehci,id=ehci"
gives you a bus named "ehci.0".
For builtin devices that doesn't work though as you don't have to add
them manually. Guess they should be explicitly named then by zynq_init().
cheers,
Gerd
next prev parent reply other threads:[~2012-12-03 13:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 2:57 [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI Andreas Färber
2012-12-02 2:57 ` [Qemu-devel] [PATCH RFT 1/5] usb/ehci: Clean up SysBus and PCI EHCI split Andreas Färber
2012-12-03 18:35 ` Igor Mitsyanko
2012-12-02 2:57 ` [Qemu-devel] [PATCH RFT 2/5] usb/ehci: Move capsbase and opregbase into SysBus EHCI class Andreas Färber
2012-12-03 18:38 ` Igor Mitsyanko
2012-12-02 2:57 ` [Qemu-devel] [PATCH RFT 3/5] usb/ehci: Add SysBus EHCI device for Exynos4210 Andreas Färber
2012-12-03 18:51 ` Igor Mitsyanko
2012-12-04 0:19 ` walimis
2012-12-04 7:14 ` walimis
2012-12-02 2:57 ` [Qemu-devel] [PATCH RFT 4/5] exynos4210: Add EHCI support Andreas Färber
2012-12-03 18:52 ` Igor Mitsyanko
2012-12-02 2:57 ` [Qemu-devel] [PATCH RFT 5/5] usb/ehci: Add Tegra2 SysBus EHCI device Andreas Färber
2012-12-02 10:34 ` [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI walimis
2012-12-02 16:27 ` Andreas Färber
2012-12-03 3:24 ` walimis
2012-12-03 6:59 ` Gerd Hoffmann
2012-12-03 11:58 ` walimis
2012-12-03 12:10 ` Peter Maydell
2012-12-03 12:38 ` walimis
2012-12-03 13:37 ` Gerd Hoffmann [this message]
2012-12-03 13:39 ` Peter Maydell
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=50BCAB2C.6040106@redhat.com \
--to=kraxel@redhat.com \
--cc=andreas.faerber@web.de \
--cc=i.mitsyanko@samsung.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vpalatin@chromium.org \
--cc=walimisdev@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 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).