> >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
