PCI range checking under qemu-system-sparc64

[Alexey Dokuchaev]

On Tue, Sep 15, 2015 at 11:14:57PM +0100, Mark Cave-Ayland wrote:
> Aha - I bet that's it. I've tweaked OpenBIOS to update phys_mid the same
> as "assigned-addresses" and that now gives me the following for /pci/ebus:
> 
> [...]
> Properly formatted, ranges now looks like this:
> 
> 00000010 00000000 02001810 00000000 03000000 01000000
> 00000014 00000000 01001814 00000000 00004000 00004000
> 
> ...and in my tests here it doesn't appear to regress any of my test
> images. As I still don't have a FreeBSD environment setup yet, I've
> uploaded the binary to http://www.ilande.co.uk/tmp/openbios-sparc64 - if
> someone with QEMU 2.4 could replace openbios-sparc64 with the downloaded
> version and post a boot log in -nographic mode then that would be great.

Log is identical to the one I posted earlier (modulo the build timestamps),
except this part:

 eeprom0: <EEPROM/clock> addr 0x1400002000-0x1400003fff on ebus0
-eeprom0: cannot allocate resources
-device_attach: eeprom0 attach returned 6
+eeprom0: model mk48t59
 ebus0: <fdthree> addr 0 (no driver attached)
-ebus0: <su> addr 0x14000003f8-0x14000003ff irq 43 (no driver attached)
+uart0: <16550 or compatible> addr 0x14000003f8-0x14000003ff irq 43 on ebus0
+uart0: console (9600,n,8,1)
 ebus0: <kb_ps2> addr 0x1400000060-0x1400000067 (no driver attached)

Kernel still hangs at the same place.

> BTW does the comment on D2791 mean that it has been superseded by a new
> patch that has been committed to trunk?

Yes, it was committed as part of r287726.  Because commit log did not have
reference to D2791, it had to be closed/abandoned by hand.

./danfe