From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: crt0: Pass malloc base address
Date: Sat, 14 Nov 2015 16:23:12 +0100 [thread overview]
Message-ID: <20151114162312.748ad9ee@lilith> (raw)
In-Reply-To: <CAPnjgZ1pKtS5ihov10Vv8cFeJnJKVpp3vXJ0SFfDq=8aH7QE5g@mail.gmail.com>
Hello Simon,
On Fri, 13 Nov 2015 19:12:13 -0700, Simon Glass <sjg@chromium.org>
wrote:
> > IMO, keeping it simple does not play well with making DM and malloc
> > available pre-SDRAM init :) --- but don't miscontrue my meaning: I'm
> > fine with DM and malloc pre-SDRAM on platforms which have enough IRAM /
> > SRAM / lockable cache / whatever for it. My point is just that sooner
> > or later, someone will start wanting not to do again after SDRAM init
> > what they've already done before it, because it avoids double HW init
> > issues, becaue it saves time, etc. And that's going to be way sooner
> > than later, IMO.
>
> Yes that is quite possibility true. I'm happy to review any patches if
> it helps. My comment about it possibly not being worthwhile solving is
> just that. Things have a way of changing, so what looks unnecessary
> now might look essential tomorrow. In a way, the simple malloc() fits
> into that category.
And so evolve the uses of DM, of the DT, etc.
Alright, so I will post my RFC and read your comments with much
interest!
> Regards,
> Simon
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-11-14 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 20:23 [U-Boot] [PATCH] ARM: crt0: Pass malloc base address Fabio Estevam
2015-11-11 20:26 ` Simon Glass
2015-11-11 20:41 ` Fabio Estevam
2015-11-11 21:00 ` Fabio Estevam
2015-11-11 21:08 ` Simon Glass
2015-11-11 21:24 ` Fabio Estevam
2015-11-11 21:49 ` Simon Glass
2015-11-12 6:57 ` Albert ARIBAUD
2015-11-12 12:48 ` Fabio Estevam
2015-11-12 15:59 ` Simon Glass
2015-11-12 16:13 ` Albert ARIBAUD
2015-11-14 2:12 ` Simon Glass
2015-11-14 15:23 ` Albert ARIBAUD [this message]
2015-11-11 20:33 ` Albert ARIBAUD
2015-11-11 20:49 ` Fabio Estevam
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=20151114162312.748ad9ee@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