From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.aribaud@free.fr>
Date: Sun, 14 Nov 2010 18:53:30 +0100
Subject: [U-Boot] RFC: Aligning arch initialisation sequences
In-Reply-To: <20101114150102.DAAF914EA7E@gemini.denx.de>
References: <4CD67A22.9040802@gmail.com>
	<201011091835.38581.vapier@gentoo.org>	<4CDE1107.80108@gmail.com>
	<4CDE4A53.4070106@free.fr>	<4CDE741C.1020507@gmail.com>
	<4CDF6F2E.9040900@gmail.com>	<4CDF7821.4080300@gmail.com>
	<4CDFA8E9.3050803@free.fr>	<20101114103001.7EE2014EA7E@gemini.denx.de>	<4CDFD1AE.1070409@free.fr>
	<20101114150102.DAAF914EA7E@gemini.denx.de>
Message-ID: <4CE0221A.7030502@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 14/11/2010 16:01, Wolfgang Denk a ?crit :

> This is perfectly OK, as we don't have to interface in any way with
> any strictly EABI conforming code - we are working in a completely
> controlled environment and can adjust rules as needed.

Alright, then I think we should document how we comply, or do not 
comply, with GNU EABI / AAPCS (maybe a README.arm that people could read 
up) -- and I think if there is a way to access GD both before and after 
relocation without making a register unavailable to the whole u-boot 
code, then we should use it.

> Best regards,
>
> Wolfgang Denk

Amicalement,
-- 
Albert.