Reviewing myself:
On Sun, 4 Nov 2012 12:32:04 +0100, Albert ARIBAUD
wrote:
> diff --git a/arch/arm/lib/crt0.S b/arch/arm/lib/crt0.S
> new file mode 100644
> index 000..fd6bd92
> --- /dev/null
> +++ b/arch/arm/lib/crt0.S
> +clbss_l:cmp r0, r1 /* while not at end of BSS */
Hi Andreas,
On Mon, 05 Nov 2012 09:31:55 +0100, "Andreas Bießmann"
wrote:
> Dear Albert Aribaud,
> DDR means DRAM in general?
Yes -- but DRAM is no better, as it still describes a technology
(class). I'm going tu use "system RAM" to describe it.
> > + *must use GD to store any data which
Dear Albert Aribaud,
On 04.11.2012 12:32, Albert ARIBAUD wrote:
> Move all the C runtime setup code from every start.S
> in arch/arm into arch/arm/lib/crt0.S. This covers
> the code sequence from isetting up the initial stack
> to calling into board_init_r().
>
> Also, rewrite the C runtime setup
Hi Vikram,
On Sun, 04 Nov 2012 20:36:14 +0530, Vikram Narayanan
wrote:
> Hello Albert,
> > diff --git a/arch/arm/lib/crt0.S b/arch/arm/lib/crt0.S
> > +#ifndef CONFIG_SPL_BUILD
>
> In some places the other style is used. "!(defined)".
> Any particular reasons for switching b/w these two styles
Hello Albert,
On 11/4/2012 5:02 PM, Albert ARIBAUD wrote:
Move all the C runtime setup code from every start.S
in arch/arm into arch/arm/lib/crt0.S. This covers
the code sequence from isetting up the initial stack
to calling into board_init_r().
Also, rewrite the C runtime setup and make functi
Hi Albert,
On Sun, 4 Nov 2012 12:32:04 +0100, Albert ARIBAUD
wrote:
> the code sequence from isetting up the initial stack
Argh. s/isetting/setting/ in V3...
Amicalement,
--
Albert.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/
Move all the C runtime setup code from every start.S
in arch/arm into arch/arm/lib/crt0.S. This covers
the code sequence from isetting up the initial stack
to calling into board_init_r().
Also, rewrite the C runtime setup and make functions
board_init_*() and relocate_code() behave according to
no
7 matches
Mail list logo