From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:47672)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas.faerber@web.de>) id 1RTgmo-00006W-US
	for qemu-devel@nongnu.org; Thu, 24 Nov 2011 16:24:51 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas.faerber@web.de>) id 1RTgmm-0004IE-GU
	for qemu-devel@nongnu.org; Thu, 24 Nov 2011 16:24:50 -0500
Received: from mout.web.de ([212.227.15.4]:49506)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas.faerber@web.de>) id 1RTgmm-0004I4-3c
	for qemu-devel@nongnu.org; Thu, 24 Nov 2011 16:24:48 -0500
Message-ID: <4ECEB5FD.6010404@web.de>
Date: Thu, 24 Nov 2011 22:24:13 +0100
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <andreas.faerber@web.de>
MIME-Version: 1.0
References: <4ECD88EF.2030200@web.de>
	<CAFEAcA-+3o997=GMh9Y6nGSW8dfg7a3v7XXK8Zyyh-vRAzGzgg@mail.gmail.com>
In-Reply-To: <CAFEAcA-+3o997=GMh9Y6nGSW8dfg7a3v7XXK8Zyyh-vRAzGzgg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] Initializing PC from memory on reset?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>

Am 24.11.2011 08:47, schrieb Peter Maydell:
> On 23 November 2011 23:59, Andreas Färber <andreas.faerber@web.de> wrote:
>> Unlike PowerPC, an architecture that I'm trying to emulate does not
>> store branch instructions in the reset vector but a memory address. I'm
>> therefore trying to read physical address 0x00000 and store its value
>> into my env->pc.
> 
> Have you looked at how M profile ARM does it? That has a similar
> "read memory for initial PC value". (There are some interesting
> wrinkles, not all of which we get quite right, regarding how this
> should interact with initial ELF image load and the user fiddling
> with PC and RAM in an attached debugger.)

Thanks. I thought I had seen something like that but apparently grep'ed
for the wrong keywords.

Can anyone enlighten me why rom_ptr()+lduw_p() works at this point in
time and lduw_phys() doesn't but later does? The MemoryRegion is
initialized as a ram area. Is this a legacy issue (pre-Memory API)?

Andreas