From: walimis <walimisdev@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>, andreas.faerber@web.de
Cc: Peter Maydell <peter.maydell@linaro.org>,
peter.crosthwaite@xilinx.com,
Igor Mitsyanko <i.mitsyanko@samsung.com>,
qemu-devel@nongnu.org, Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI
Date: Mon, 3 Dec 2012 19:58:12 +0800 [thread overview]
Message-ID: <20121203115812.GC6029@pek-lwang0-d1> (raw)
In-Reply-To: <50BC4DEB.7080303@redhat.com>
On Mon, Dec 03, 2012 at 07:59:55AM +0100, Gerd Hoffmann wrote:
> Hi,
>
>> Gerd: In order for me to use this with the new-style Tegra2 model we
>> will need to further move EHCISysBusState and the accompanying macros
>> that this series adds into the hcd-ehci.h header so that it can be
>> embedded into the SoC object. So if you're okay with my approach we'd
>> need a v2.
>
>Looks good to me. Guess we want something simliar for UHCI ...
>
>> Also a question: Vincent's patch has a comment "multiple EHCI
>> controllers support not ready". Is this still a known issue or resolved
>> by now?
>
>I'm not aware of any.
Hi Andreas,
I'm aware of it today.
For example, xilinx_zynq has two EHCI controllers. If I specify a usb
device of type "usb-storage", the question is: which EHCI controller does the
usb device attach to? The answer is dependent.
1. If I use "usbdevice" and pass the host usb device, such as:
$ qemu -usb -usbdevice host:xxxx:xxxx
The device will attach to the first EHCI controller.
2. If I use "device" and "usb-storage", such as:
$ qemu -usb -device usb-storage,drive=ud -drive id=ud,file=usbdisk.img,if=none
The device will attach to the second EHCI controller.
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.
Liming Wang
>
>cheers,
> Gerd
next prev parent reply other threads:[~2012-12-03 11:58 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 [this message]
2012-12-03 12:10 ` Peter Maydell
2012-12-03 12:38 ` walimis
2012-12-03 13:37 ` Gerd Hoffmann
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=20121203115812.GC6029@pek-lwang0-d1 \
--to=walimisdev@gmail.com \
--cc=andreas.faerber@web.de \
--cc=i.mitsyanko@samsung.com \
--cc=kraxel@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vpalatin@chromium.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).