public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] common: board: support systems with where RAM ends beyond 4GB
Date: Thu, 22 Jan 2015 11:06:33 -0700	[thread overview]
Message-ID: <54C13C29.9060304@wwwdotorg.org> (raw)
In-Reply-To: <1256a00bff254a2d8036aae2574c7509@HQMAIL103.nvidia.com>

On 01/20/2015 08:56 AM, Tom Warren wrote:
> I've merged that patch series w/u-boot-tegra/next and /master, done a MAKEALL -s tegra, and rebased against ARM /master and pushed to denx.de.
>
> Stephen - please test and if it looks OK, I'll prepare a PR.

This works great on my Jetson TK1. Thanks.

>
>> -----Original Message-----
>> From: Tom Warren
>> Sent: Tuesday, January 20, 2015 8:28 AM
>> To: 'Stephen Warren'; u-boot at lists.denx.de; Simon Glass; Stephen Warren
>> Cc: Tom Rini
>> Subject: RE: [U-Boot] [PATCH 1/3] common: board: support systems with
>> where RAM ends beyond 4GB
>>
>> Sorry, missed this. Yes, looks good to me. I can apply it to u-boot-
>> tegra/master, or TomR can take it in to master U-Boot directly.
>>
>> Tom
>>
>>> -----Original Message-----
>>> From: Stephen Warren [mailto:swarren at wwwdotorg.org]
>>> Sent: Monday, January 19, 2015 3:57 PM
>>> To: u-boot at lists.denx.de; Simon Glass; Tom Warren; Stephen Warren
>>> Cc: Tom Rini
>>> Subject: Re: [U-Boot] [PATCH 1/3] common: board: support systems with
>>> where RAM ends beyond 4GB
>>>
>>> On 12/23/2014 10:34 AM, Stephen Warren wrote:
>>>> From: Stephen Warren <swarren@nvidia.com>
>>>>
>>>> Some systems have so much RAM that the end of RAM is beyond 4GB.
>> An
>>>> example would be a Tegra124 system (where RAM starts at 2GB
>>>> physical) that has more than 2GB of RAM.
>>>>
>>>> In this case, we can gd->ram_size to represent the actual RAM size,
>>>> so that the actual RAM size is passed to the OS. This is useful if
>>>> the OS implements LPAE, and can actually use the "extra" RAM.
>>>>
>>>> However, U-Boot does not implement LPAE and so must deal with 32-bit
>>>> physical addresses. To this end, we enhance
>>>> board_get_usable_ram_top() to detect the "over-sized" case, and
>>>> limit the relocation addres so that it fits into 32-bits of physical address
>> space.
>>>
>>> TomW, TomR, does this series look good?
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information.  Any unauthorized review, use, disclosure or distribution
> is prohibited.  If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
>

      reply	other threads:[~2015-01-22 18:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 17:34 [U-Boot] [PATCH 1/3] common: board: support systems with where RAM ends beyond 4GB Stephen Warren
2014-12-23 17:34 ` [U-Boot] [PATCH 2/3] ARM: tegra: fix variable naming in query_sdram_size() Stephen Warren
2014-12-23 20:02   ` Simon Glass
2014-12-23 17:34 ` [U-Boot] [PATCH 3/3] ARM: tegra: support large RAM sizes Stephen Warren
2014-12-23 20:05   ` Simon Glass
2014-12-23 20:34     ` Stephen Warren
2014-12-23 22:18       ` Simon Glass
2014-12-23 20:01 ` [U-Boot] [PATCH 1/3] common: board: support systems with where RAM ends beyond 4GB Simon Glass
2014-12-23 20:22   ` Stephen Warren
2014-12-23 20:26     ` Simon Glass
2015-01-19 22:57 ` Stephen Warren
2015-01-20 15:28   ` Tom Warren
2015-01-20 15:56   ` Tom Warren
2015-01-22 18:06     ` Stephen Warren [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=54C13C29.9060304@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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