qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: walimis <walimisdev@gmail.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: david.holsgrove@xilinx.com, john.williams@xilinx.com,
	qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1.3] ehci-sysbus: Attach DMA context.
Date: Mon, 3 Dec 2012 20:03:10 +0800	[thread overview]
Message-ID: <20121203120309.GD6029@pek-lwang0-d1> (raw)
In-Reply-To: <CAEgOgz4VW9gOe4s5A2RXSB9N3-dk6R1+Y1Yxc6tyiZCdjSHXDg@mail.gmail.com>

On Thu, Nov 29, 2012 at 12:05:14PM +1000, Peter Crosthwaite wrote:
>On Thu, Nov 29, 2012 at 12:00 PM, walimis <walimisdev@gmail.com> wrote:
>> On Thu, Nov 29, 2012 at 11:43:18AM +1000, Peter Crosthwaite wrote:
>>>This was left as NULL on the initial merge due to debate on the mailing list on
>>>how to handle DMA contexts for sysbus devices. Patch
>>>9e11908f12f92e31ea94dc2a4c962c836cba9f2a was later merged to fix OHCI. This is the,
>>>equivalent fix for sysbus EHCI.
>>
>> I have also found this issue, but it's not the cause that xilinx
>> ehci can't work with usb-storage disk. Do you have any update
>> for xilinx ehci?
>>
>
>Hi Liming,
>
>I haven't got around to looking into that one yet unfortunately. No
>updates just yet - ill let you know if it resolves. It could very well
>be a Linux bug as well so it needs to be investigated from both sides
>of the fence.

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 now, qemu doesn't support two EHCI controller, could we remove the second
EHCI from xilinx_zynq?

Liming Wang

>
>>>
>>>Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
>>
>> Tested-by: Liming Wang <walimisdev@gmail.com>
>>
>
>Thanks.
>
>Regards,
>Peter
>
>> Liming Wang
>>
>>>---
>>> hw/usb/hcd-ehci-sysbus.c |    1 +
>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>>diff --git a/hw/usb/hcd-ehci-sysbus.c b/hw/usb/hcd-ehci-sysbus.c
>>>index 1584079..803df92 100644
>>>--- a/hw/usb/hcd-ehci-sysbus.c
>>>+++ b/hw/usb/hcd-ehci-sysbus.c
>>>@@ -45,6 +45,7 @@ static int usb_ehci_sysbus_initfn(SysBusDevice *dev)
>>>
>>>     s->capsbase = 0x100;
>>>     s->opregbase = 0x140;
>>>+    s->dma = &dma_context_memory;
>>>
>>>     usb_ehci_initfn(s, DEVICE(dev));
>>>     sysbus_init_irq(dev, &s->irq);
>>>--
>>>1.7.0.4
>>>
>>>
>>

  reply	other threads:[~2012-12-03 12:03 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 [this message]
2012-12-03 12:51       ` Gerd Hoffmann
2012-12-03 14:50         ` walimis
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=20121203120309.GD6029@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).