From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.aribaud@free.fr>
Date: Mon, 15 Nov 2010 15:29:47 +0100
Subject: [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld
	support
In-Reply-To: <20101115140647.GB22583@bee.dooz.org>
References: <4CDA9096.2080505@schmid-telecom.ch>
	<4CDA9489.6030108@free.fr>	<4CDA9CF2.1030202@schmid-telecom.ch>
	<4CDBA515.3050106@free.fr>	<20101114212240.5FA7914EA7E@gemini.denx.de>	<4CE11314.50807@free.fr>	<20101115111321.50761134FEF@gemini.denx.de>	<4CE11E66.5060207@free.fr>
	<20101115115556.GA13479@bee.dooz.org>	<20101115120354.866DB134FEF@gemini.denx.de>
	<20101115140647.GB22583@bee.dooz.org>
Message-ID: <4CE143DB.6050907@free.fr>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Le 15/11/2010 15:06, Lo?c Minier a ?crit :

>   So I'm afraid I couldn't find a fully working combination of U-Boot
>   supported board + QEMU, but I didn't try QEMU tip; I'm Cc:ing Peter who
>   cares for QEMU in Linaro, maybe he has more idea or is tempted to try a
>   tip QEMU  :-)

Not sure I get how this works. Do you need to build u-boot in a special 
way or with a special toolchain in order to run it in qemu? I'm asking 
because:

>   If you want to reproduce, run something like:
>      qemu-system-arm -M versatilepb -serial stdio \
>          -kernel u-boot_bin_u-boot_versatilepb.axf

I assume that the -kernel option indicates the executable to run. Would 
it take an ELF executable? a binary? How would one go about testing 
running u-boot from RAM, NOR, NAND?

Also:

>   [1] crashes while initializing the NIC; qemu: hardware error:
>       smc91c111_write: Bad reg 0:6
>   [2] qemu: hardware error: arm_timer_write: Bad offset 101e1fe0
>   [3] qemu: hardware error: pl011_write: Bad offset 14
>   [4] crashes after detecting 0 Bytes of DRAM:

This seems to mean the HW is not 100% simulated, right?

One last question:

>      qemu: fatal: Trying to execute code outside RAM or ROM at 0x34000000

Does this mean that qemu does not simulate data or instruction aborts? 
Not that it is required for u-boot, but it *could* be useful sometimes.

Amicalement,
-- 
Albert.