From: walimis <walimisdev@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
john.williams@xilinx.com, david.holsgrove@xilinx.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.3] ehci-sysbus: Attach DMA context.
Date: Mon, 3 Dec 2012 22:50:20 +0800 [thread overview]
Message-ID: <20121203145020.GF6029@pek-lwang0-d1> (raw)
In-Reply-To: <50BCA034.2090301@redhat.com>
On Mon, Dec 03, 2012 at 01:51:00PM +0100, Gerd Hoffmann wrote:
> Hi,
>
>> As said in another mail, I found that the root cause is that xilinx_zynq has
>> two EHCI controller. If we use usb-storage disk, the disk will be attached to
>> the second EHCI controller, which the kernel uses the first EHCI controller
>> by default.
>
>For the linux kernel it shouldn't matter where the usb stick is
>connected. Assuming it finds both ehci controllers. Does it?
The default device tree of linux kernel has only the first ehci controller
support, so the kernel can't detect the second controller.
But the usb-storage disk is attached to the second controller, so that
the disk is failed to be detected by the linux kernel.
>
>> For now, qemu doesn't support two EHCI controller, could we remove the second
>> EHCI from xilinx_zynq?
>
>Two controllers should work just fine. I'd suggest to find the root
Yes, they work fine separately, but I don't know how to use them at the
same time (I mean both controller have device attached) as I have
mentioned in the another mail.
Liming Wang
>cause instead of doctoring like this. ehci + usb core are fine with two
>controllers & busses, maybe the arch plumbing (device tree?) misses
>something so the linux kernel doesn't find the second ehci controller.
>
>cheers,
> Gerd
>
next prev parent reply other threads:[~2012-12-03 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 1:43 [Qemu-devel] [PATCH 1.3] ehci-sysbus: Attach DMA context Peter Crosthwaite
2012-11-29 2:00 ` walimis
2012-11-29 2:05 ` Peter Crosthwaite
2012-12-03 12:03 ` walimis
2012-12-03 12:51 ` Gerd Hoffmann
2012-12-03 14:50 ` walimis [this message]
2012-12-04 5:16 ` Peter Crosthwaite
2012-12-04 6:49 ` walimis
2012-12-04 8:15 ` Gerd Hoffmann
2012-12-05 7:07 ` Peter Crosthwaite
2012-11-29 6:57 ` Gerd Hoffmann
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=20121203145020.GF6029@pek-lwang0-d1 \
--to=walimisdev@gmail.com \
--cc=david.holsgrove@xilinx.com \
--cc=john.williams@xilinx.com \
--cc=kraxel@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--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).