From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:49929) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UZSU5-0003XI-OT for qemu-devel@nongnu.org; Mon, 06 May 2013 16:58:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UZSU0-00021I-UN for qemu-devel@nongnu.org; Mon, 06 May 2013 16:58:09 -0400 Message-ID: <5188194D.7010101@reactos.org> Date: Mon, 06 May 2013 22:57:49 +0200 From: =?UTF-8?B?SGVydsOpIFBvdXNzaW5lYXU=?= MIME-Version: 1.0 References: <1367525344-7755-1-git-send-email-hpoussin@reactos.org> <1367525344-7755-2-git-send-email-hpoussin@reactos.org> <30C12B1E-5007-4B74-9A14-8F21C2D1F369@suse.de> <518351BA.1060603@reactos.org> <5187C5CA.2060805@suse.de> In-Reply-To: <5187C5CA.2060805@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/7] pci: add MPC105 PCI host bridge emulation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "qemu-ppc@nongnu.org" , "qemu-devel@nongnu.org" , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Alexander Graf a =C3=A9crit : > On 05/03/2013 07:57 AM, Herv=C3=A9 Poussineau wrote: >> Alexander Graf a =C3=A9crit : >>> >>> Am 02.05.2013 um 22:08 schrieb Herv=C3=A9 Poussineau : >>> >>>> Non-contiguous I/O is not implemented. >>>> >>>> There is also somewhere a bug in the memory controller, which means >>>> that some real firmwares may not detect the correct amount of memory= . >>>> This can be bypassed by adding '-m 1G' on the command line. >>>> >>>> Add x-auto-conf property, to automatically configure the memory >>>> controller at startup. This will be required by OpenBIOS, which >>>> doesn't know how to do it. >>> >>> Why not teach it? I'd prefer to see that logic in firmware. >> >> Me too, but I'm not confident enough in my capabilities to do it. >=20 > Huh? Why not? Most of the device initialization code in OpenBIOS happen= s=20 > in C, so you don't even have to touch Forth code :). >=20 >> Autoconfiguration is only in one place of the code, so I think it can=20 >> be removed easily once OpenBIOS has this logic. >=20 > I'd prefer if we could come up with a clean model from the start. It=20 > really shouldn't be hard at all. >=20 I thought that for all other usages of OpenBIOS in QEMU, RAM was=20 supposed to be available as soon as machine was powered on. However, I checked OpenBIOS code: One of the first things done in arch/ppc/qemu/start.S is to copy the=20 exception vectors. So, I should add code before it to detect memory=20 controller, detect ram size and configure memory controller? It seems quite a bit of code. Do you have an example of how to do it for another memory controller, so=20 I can adapt the code? Regards, Herv=C3=A9