public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Oliver Schinagl <oliver+list@schinagl.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ARM: U-boot and 2 GiB of ram with get_ram_size only being long
Date: Sat, 19 Oct 2013 01:07:58 +0200	[thread overview]
Message-ID: <5261BF4E.9070301@schinagl.nl> (raw)
In-Reply-To: <1382114601.7979.843.camel@snotra.buserror.net>

On 10/18/13 18:43, Scott Wood wrote:
> On Fri, 2013-10-18 at 02:04 +0200, Oliver Schinagl wrote:
>> So now that that's settled, anything fundamentally wrong with my patch? :)
>
> Did you see my other mail in this thread?  This patch is sort of OK for
Sorry I did and I got distracted from it.

> raising the get_ram_size() limit from 1 GiB to 2 GiB (with an increased
> risk of false positives from I/O), but it can't go beyond that on
I'd ask 'how so' but I'm not sure I'd understand anyway ;)

> 32-bit.  A better approach would be to get the RAM size from the memory
> controller, which is what we do on many Freescale PPC boards.
Not possible for us at this moment. The memory controller is programed 
with hard-coded values on a per board basis. I think we could 
technically obtain values via/from the memory controller, but have no 
knowledge at this moment. Allwinner has a tool, livesuit, which is used 
to flash full disk images to a device. We currently guesstimate that 
livesuit can somehow detect the memory parameters and injects it into 
the stock bootloader. But we really have no clue if that really happens 
or how it's done. So we rely on extracting the information from a 
running stock android/linux and hardcode it into u-boot.

Oliver

>
> -Scott
>
>
>

  parent reply	other threads:[~2013-10-18 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 21:15 [U-Boot] [RFC] ARM: U-boot and 2 GiB of ram with get_ram_size only being long Oliver Schinagl
2013-10-07  2:41 ` Oliver Schinagl
2013-10-15  7:12   ` Albert ARIBAUD
2013-10-15 17:57     ` Scott Wood
2013-10-17  6:27       ` Albert ARIBAUD
2013-10-18  0:04         ` Oliver Schinagl
2013-10-18 16:43           ` Scott Wood
2013-10-18 20:26             ` Wolfgang Denk
2013-10-18 21:04               ` Scott Wood
2013-10-18 21:53                 ` Wolfgang Denk
2013-10-18 23:11               ` Oliver Schinagl
2013-10-18 23:07             ` Oliver Schinagl [this message]
2013-10-18 23:25               ` Scott Wood
2013-10-18 23:25                 ` Scott Wood
2013-10-19  9:21                   ` Oliver Schinagl
2013-10-19  9:07                 ` Oliver Schinagl
2013-10-19 18:25                   ` Tom Rini
2013-10-21 19:44                 ` Wolfgang Denk
2014-03-24 10:14                   ` Olliver Schinagl
2013-10-15 18:01 ` Scott Wood

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=5261BF4E.9070301@schinagl.nl \
    --to=oliver+list@schinagl.nl \
    --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