From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Skipping relocation RAM to RAM, esp. on i.MX6?
Date: Wed, 08 Feb 2012 12:13:52 +0530 [thread overview]
Message-ID: <4F3219A8.7090607@ti.com> (raw)
In-Reply-To: <20120207232605.3009682373@gemini.denx.de>
Dear Wolfgang,
On Wednesday 08 February 2012 04:56 AM, Wolfgang Denk wrote:
> Dear Aneesh V,
>
> In message<4F30D06E.8060200@ti.com> you wrote:
>>
>> I agree. Even on some platforms that are not fully static (such as having
>> variants with different memory sizes) the minimum available memory is
>> more than enough to allocate big enough partitions for each need at
>> U-Boot level. And my guess (or rather speculation) is that platforms
>> that do not have any real dynamic needs are in the majority. I sincerely
>> believe that platforms should be allowed to enable/disable
>> relocation based on their needs.
>
> This is your opinion. It is noted, and appreciated.
>
> But you should not try to continue to ignore all the previous
> discussion to that topic. There have been no new arguments in this
> round, so there will be no change of the previously made decisions.
First of all I am not arguing in favor of taking it in the current
form. But as Graeme mentioned if the new initcall framework makes it
clean and maintainable I am hoping that you will consider it more
favorably. And this is indeed a new argument because the biggest
objection previously was that the no-relocation case will be difficult
to maintain.
As for ignoring comments, I think you are culpable of that more than me
in this specific instance:) (of course I know you are busy person, but
still..). For instance, my arguments in the previous round [1] never
got an answer from you.
[1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/96371
best regards,
Aneesh
next prev parent reply other threads:[~2012-02-08 6:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 7:25 [U-Boot] Skipping relocation RAM to RAM, esp. on i.MX6? Dirk Behme
2012-02-03 8:51 ` Stefano Babic
2012-02-03 10:18 ` Dirk Behme
2012-02-03 11:00 ` Stefano Babic
2012-02-03 11:19 ` Mike Frysinger
2012-02-04 8:38 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling (was: Re: Skipping relocation RAM to RAM, esp. on i.MX6?) Dirk Behme
2012-02-04 9:18 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling Aneesh V
2012-02-04 10:18 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling (was: Re: Skipping relocation RAM to RAM, esp. on i.MX6?) Marek Vasut
2012-02-08 13:37 ` [U-Boot] i.MX5/6 U-Boot: Cache enabling Dirk Behme
2012-02-09 7:06 ` Marek Vasut
2012-02-04 9:15 ` [U-Boot] Skipping relocation RAM to RAM, esp. on i.MX6? Aneesh V
2012-02-04 11:00 ` Albert ARIBAUD
2012-02-04 11:14 ` Aneesh V
2012-02-04 11:37 ` Albert ARIBAUD
2012-02-06 14:34 ` Tom Rini
2012-02-06 21:21 ` Albert ARIBAUD
2012-02-06 22:27 ` Wolfgang Denk
2012-02-06 22:41 ` Graeme Russ
2012-02-07 7:19 ` Aneesh V
2012-02-07 23:26 ` Wolfgang Denk
2012-02-08 6:43 ` Aneesh V [this message]
2012-02-08 13:58 ` Wolfgang Denk
2012-02-08 14:48 ` Aneesh V
2012-02-08 16:23 ` Wolfgang Denk
2012-02-09 6:01 ` Aneesh V
2012-02-09 11:44 ` Wolfgang Denk
2012-02-09 13:43 ` Aneesh V
2012-02-05 6:19 ` Simon Glass
2012-02-06 14:19 ` Aneesh V
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=4F3219A8.7090607@ti.com \
--to=aneesh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.