From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] RFC: am35xx: Rearrange SPL on am35xx
Date: Fri, 19 Dec 2014 13:53:26 +0100 [thread overview]
Message-ID: <20141219135326.1586cecd@lilith> (raw)
In-Reply-To: <1418927172-24834-1-git-send-email-sjg@chromium.org>
Hello Simon,
On Thu, 18 Dec 2014 11:26:12 -0700, Simon Glass <sjg@chromium.org>
wrote:
> This is an attempt to tidy up the early SPL code in an attempt to pave
> the way for driver model in SPL:
>
> - Avoid setting up SDRAM before board_init_f()
> - Avoid touching global_data before board_init_f()
By 'touching', do you mean writing or just reading?
> - Allow board_init_f() to set up a new stack (seems that the SRAM stack
> is not large enough on these boards)
I would prefer board_init_f() not to set up or change the stack.
Can't we keep board_init_f() minimal (i.e., just doing what's needed to
get DRAM working) with a minimal stack, then let crt0.S switch stacks,
and put whatever requires a larg(er) stack in board_init_r?
IOW, what prevents the general boot flow (and stack management) which
crt0.S applies to U-Boot from applying to SPL too?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-12-19 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 18:26 [U-Boot] [PATCH] RFC: am35xx: Rearrange SPL on am35xx Simon Glass
2014-12-19 12:53 ` Albert ARIBAUD [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-19 0:21 Simon Glass
2014-12-19 14:40 ` Tom Rini
2014-12-19 15:32 ` Simon Glass
2014-12-21 12:30 ` Tom Rini
2014-12-21 18:53 ` Simon Glass
2014-12-21 19:29 ` Tom Rini
2014-12-21 23:15 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141219135326.1586cecd@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox