Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Sep 2015 10:39:41 +0000
From:      Alexey Dokuchaev <danfe@FreeBSD.org>
To:        Marius Strobl <marius@alchemy.franken.de>
Cc:        Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org>
Subject:   Re: PCI range checking under qemu-system-sparc64
Message-ID:  <20150913103940.GA60101@FreeBSD.org>
In-Reply-To: <20150913022143.GA7862@alchemy.franken.de>
References:  <557DA6D5.4070800@FreeBSD.org> <557DCF54.7020606@ilande.co.uk> <A88F6A52-FA8A-4669-A2D6-23374F8E26BB@FreeBSD.org> <557DF887.20508@ilande.co.uk> <20150906110308.GA68829@FreeBSD.org> <55EC2E8D.4020803@ilande.co.uk> <20150906124859.GA14919@FreeBSD.org> <20150907203152.GA70457@alchemy.franken.de> <55EDFE00.9090109@ilande.co.uk> <20150913022143.GA7862@alchemy.franken.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 13, 2015 at 04:21:43AM +0200, Marius Strobl wrote:
> However, looking at ebus(4), I've spotted a bug in the conversion
> to NEW_PCIB. Interested parties might want to give the attached
> patch a try. That bug definitely can lead to the problem seen with
> QEMU, I'm not sure it's the only one in that regard, though; I'm
> fairly certain in this case there's no problem with interpreting
> the device-tree involved, given that the same code is used for
> ISA busses which - at least in reality - unlike EBus ones use
> I/O port instead of memory space for the resources of devices
> such as UARTs etc. There could be other spots not prepared for
> EBus devices suddenly requesting SYS_RES_IOPORT, too, though.

I've applied that patch, but it alone is not enough to allow the boot
to proceed further in QEMU. :(

As Mark had mentioned, I will try to get some debug info and share
it if I find anything interesting.

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150913103940.GA60101>