From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XIad2-0003XT-3W for qemu-devel@nongnu.org; Sat, 16 Aug 2014 05:50:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XIacw-00066K-3T for qemu-devel@nongnu.org; Sat, 16 Aug 2014 05:50:28 -0400 Received: from mail-we0-x231.google.com ([2a00:1450:400c:c03::231]:57782) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XIacv-00066G-TD for qemu-devel@nongnu.org; Sat, 16 Aug 2014 05:50:22 -0400 Received: by mail-we0-f177.google.com with SMTP id w62so3099732wes.8 for ; Sat, 16 Aug 2014 02:50:21 -0700 (PDT) Received: from localhost (109241087153.gdansk.vectranet.pl. [109.241.87.153]) by mx.google.com with ESMTPSA id o2sm15373978wij.24.2014.08.16.02.50.19 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Aug 2014 02:50:20 -0700 (PDT) Date: Sat, 16 Aug 2014 11:50:18 +0200 From: Piotr =?iso-8859-1?Q?Kr=F3l?= Message-ID: <20140816095017.GB25591@echad> References: <20140815100719.GB11560@echad> <20140815180221.GA25591@echad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] vexpress-a9: coreboot is unable to push any data on stack List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developers On Fri, Aug 15, 2014 at 11:54:55PM +0100, Peter Maydell wrote: > I'm not looking for advocacy, just for an explanation of what it's > doing, and in particular whether anybody's ever tested this on real > hardware. (Running guest code only on QEMU is a recipe for bugs, > because our emulation is often not very accurate and if you only test > on QEMU you can end up accidentally relying on our bugs.) > Creboot is an open source replacement for BIOS. Almost every supported board contain its own memory map. According to commit message from Chromium developer coreboot build for qemu vexpress-a9 was created to 'simplify testing ARM implementation (... and) to verify the boot loader functionality'. I think that code for real hardware got little in common with qemu implementation. I'm trying to use this implementation for pure educational purposes. Going back to my initial issues with stack, changing stack location to SRAM improves situation but does not fix booting. It looks like whole implementation assumes running from RAM. > The common motherboard docs: > http://infocenter.arm.com/help/topic/com.arm.doc.dui0447j/index.html > A9 daughterboard docs: > http://infocenter.arm.com/help/topic/com.arm.doc.dui0448h/index.html > A15 daughterboard docs: > http://infocenter.arm.com/help/topic/com.arm.doc.dui0604e/index.html > Thanks, Piotr