From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Use .data section in SPL ?
Date: Wed, 10 Dec 2014 21:04:47 -0500 [thread overview]
Message-ID: <20141211020447.GU20704@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0deAK0Gov75eRckzRDzMj3MygLym+z3VJ9or+f2FJQpA@mail.gmail.com>
On Wed, Dec 10, 2014 at 06:56:02PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On 10 December 2014 at 07:06, Tom Rini <trini@ti.com> wrote:
> > On Wed, Dec 10, 2014 at 04:39:39PM +0900, Masahiro Yamada wrote:
> >> Hi.
> >>
> >>
> >> I notice SPL is using .data section
> >>
> >>
> >>
> >> u32 *boot_params_ptr = NULL;
> >> struct spl_image_info spl_image;
> >>
> >> /* Define board data structure */
> >> static bd_t bdata __attribute__ ((section(".data")));
> >>
> >>
> >>
> >> If SPL is running on an execute-in-place device such NOR flash,
> >> .data section is not writable.
> >>
> >> common/spl/spl_nor.c does not work.
> >
> > spl_nor.c only works today on PowerPC where there's nothing shoved into
> > the .data section.
> >
> > And all of this is related to what's needed to enable DM in SPL on ARM
> > as well, iirc anyhow.
>
> Can you please explain the SPL problem on ARM a bit more? If It could
> understand what is going on, or how to repeat it, I might be able to
> help. I'd really like to enable this DM SPL support...
Did you see the WIP patch I sent out in reply to the SPL DM series?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141210/62adc49e/attachment.pgp>
next prev parent reply other threads:[~2014-12-11 2:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 7:39 [U-Boot] Use .data section in SPL ? Masahiro Yamada
2014-12-10 14:06 ` Tom Rini
2014-12-11 1:56 ` Simon Glass
2014-12-11 2:04 ` Tom Rini [this message]
2014-12-11 2:13 ` Simon Glass
2014-12-11 2:20 ` Tom Rini
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=20141211020447.GU20704@bill-the-cat \
--to=trini@ti.com \
--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