From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] armv8: fsl-layerscale: Rewrite reserving memory for MC and debug server
Date: Wed, 18 Nov 2015 15:01:08 -0800 [thread overview]
Message-ID: <564D0334.3010704@freescale.com> (raw)
In-Reply-To: <1447887389.27264.99.camel@freescale.com>
On 11/18/2015 02:56 PM, Scott Wood wrote:
<snip>
>
>>> I think it'd be a bit more straightforward for this to return the new
>>> ram_top
>>> rather than the size to be subtracted.
>>
>> That will be inaccurate. For layerscape SoCs, the gd->ram_size is known at
>> this
>> point, but the address is not known until later in board file dram bank is
>> filled int. So this function can only return how much memory is reserved.
>
> Sorry, I should have said offset from the start of RAM instead of address. So
> the caller does "gd->ram_size = board_reserve_ram_top(gd->ram_size);".
>
Sure. That can be arranged.
York
prev parent reply other threads:[~2015-11-18 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:05 [U-Boot] [PATCH v2] armv8: fsl-layerscale: Rewrite reserving memory for MC and debug server York Sun
2015-11-18 22:15 ` Scott Wood
2015-11-18 22:48 ` York Sun
2015-11-18 22:56 ` Scott Wood
2015-11-18 23:01 ` York Sun [this message]
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=564D0334.3010704@freescale.com \
--to=yorksun@freescale.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