From: Gerd Hoffmann <kraxel@redhat.com>
To: luigi burdo <intermediadc@hotmail.com>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ppce500 usb-ehci-pci issue on last uboot
Date: Tue, 14 Nov 2017 14:33:49 +0100 [thread overview]
Message-ID: <20171114133349.jqymk3jxore4muad@sirius.home.kraxel.org> (raw)
In-Reply-To: <AM5P194MB0132CA048F3B648CB0A47DCDC8790@AM5P194MB0132.EURP194.PROD.OUTLOOK.COM>
> >How can this be reproduced?
>
> or just download my last e500 uboot build from here https://www.dropbox.com/s/xxlu6ivg3izlqvu/u-boot?dl=0
>
> qemu-system-ppc64 -M ppce500 -cpu e5500 -m 512 -bios (path to the uboot image) -device usb-ehci (or another qemulated ehci pci device) -serial stdio
>
> when the machine run and you have the uboot prompt just do "usb
> start" and you will see the hang for some second of the machine and
> after the report from uboot of an error of the ehci.
Finally found the time to look at this. Seems to not be ehci-related at
all. ehci doesn't see any mmio activity.
>From "info mtree" monitor command:
memory-region: pci bus memory
0000000000000000-ffffffffffffffff (prio 0, i/o): pci bus memory
0000000000080000-0000000000080fff (prio 1, i/o): ehci
0000000c00004000-0000000c00007fff (prio 1, i/o): virtio-pci
memory-region: system
0000000000000000-ffffffffffffffff (prio 0, i/o): system
0000000000000000-000000001fffffff (prio 0, ram): mpc8544ds.ram
0000000c00000000-0000000c1fffffff (prio 0, i/o): alias PCI Outbound Window 1 @pci bus memory 0000000c00000000-0000000c1fffffff
Seems the ehci mmio bar is mapped outside the pci window, so the cpu
can't access it ...
cheers,
Gerd
prev parent reply other threads:[~2017-11-14 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 19:10 [Qemu-devel] ppce500 usb-ehci-pci issue on last uboot luigi burdo
2017-09-27 11:34 ` Gerd Hoffmann
2017-09-27 12:21 ` luigi burdo
2017-09-28 7:27 ` luigi burdo
2017-09-28 8:07 ` Gerd Hoffmann
2017-09-28 8:28 ` luigi burdo
2017-11-14 13:33 ` Gerd Hoffmann [this message]
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=20171114133349.jqymk3jxore4muad@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=intermediadc@hotmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.