From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] tegra: add a method to query RAM size from hardware
Date: Tue, 29 May 2012 16:12:49 -0600 [thread overview]
Message-ID: <4FC549E1.6090705@wwwdotorg.org> (raw)
In-Reply-To: <1338328033-8597-1-git-send-email-dev@lynxeye.de>
On 05/29/2012 03:47 PM, Lucas Stach wrote:
> The RAM configuration is set by the bootrom to values specified by the BCT.
> To query the available RAM size of a board we can easily read back those
> values instead of using the hardcoded ODMdata. This allows for a single
> u-boot image on similar boards with different amount of RAM.
While this probably works fine (although I didn't read it in detail),
the boot protocol is defined to work a little differently. U-Boot is
supposed to read the BCT/BIT from the IRAM, and program PMC_SCRATCH20
with the ODMDATA, and then the rest of the bootloader and kernel can
continue to use the fields in the ODMDATA as they currently do.
Tom, you wrote commit f22c431 "arm: Tegra: Use ODMDATA from BCT in IRAM"
in our downstream tree for this. Are you planning on upstreaming it?
next prev parent reply other threads:[~2012-05-29 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:47 [U-Boot] [PATCH 1/3] tegra: add a method to query RAM size from hardware Lucas Stach
2012-05-29 21:47 ` [U-Boot] [PATCH 2/3] tegra: add ULPI on USB2 funcmux entry Lucas Stach
2012-05-29 22:16 ` Stephen Warren
2012-05-29 21:47 ` [U-Boot] [PATCH 3/3] tegra: usb: fix wrong error check Lucas Stach
2012-05-29 22:18 ` Stephen Warren
2012-05-29 23:20 ` Tom Warren
2012-05-29 22:12 ` Stephen Warren [this message]
2012-05-29 23:19 ` [U-Boot] [PATCH 1/3] tegra: add a method to query RAM size from hardware Tom Warren
2012-05-29 23:47 ` Stephen Warren
2012-05-30 16:04 ` Tom Warren
2012-05-30 16:37 ` Stephen Warren
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=4FC549E1.6090705@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