From mboxrd@z Thu Jan  1 00:00:00 1970
From: Reinhard Meyer <u-boot@emk-elektronik.de>
Date: Sat, 14 Aug 2010 22:47:33 +0200
Subject: [U-Boot] Struct SoC access
In-Reply-To: <4C66F54D.2060701@emk-elektronik.de>
References: <4C665CB9.2040406@emk-elektronik.de>	<20100814143009.A18461606A5@gemini.denx.de>	<4C66CCCF.9080303@emk-elektronik.de>	<20100814184641.981AC1606A5@gemini.denx.de>	<4C66EECA.5020509@emk-elektronik.de>	<20100814194117.982C71606A5@gemini.denx.de>
	<4C66F54D.2060701@emk-elektronik.de>
Message-ID: <4C6700E5.2070009@emk-elektronik.de>
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

> Would the toolchain "gulp" when one defines the whole 4 GB that way?

In fact, a rather novel approach (just theorizing here):

#define SRAM_BASE offsetof(soc.sram)
#define SRAM_SIZE sizeof(soc.sram)

dbu_t *dbu = (dbu_t *)offsetof(soc.dbu);

without ever assigning soc the address 0...

Reinhard