From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: pRAM support?
Date: Wed, 22 Jul 2009 07:49:33 +0200 [thread overview]
Message-ID: <4A66A86D.7070200@denx.de> (raw)
In-Reply-To: <1248165758.4548.10.camel@chber1-10446x.ch.keymile.net>
Hello Andreas,
Andreas Huber wrote:
> We are using the pRAM feature (CONFIG_PRAM) on the PPC architecture. As
> we are switching to an ARM architecture (Kirkwood) I am wondering if
> there is an equivalent U-Boot feature for this (CONFIG_PRAM did not
> work).
As this functionality uses RAM at the end of RAM, it should be possible
to add this also to ARM plattforms. Jean-Christophe, Prafulla, are there
any objections on it?
thanks
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-07-22 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 8:42 [U-Boot] arm: pRAM support? Andreas Huber
2009-07-22 5:49 ` Heiko Schocher [this message]
2009-07-22 7:06 ` Wolfgang Denk
2009-07-22 13:47 ` Holger brunck
2009-07-22 15:16 ` Wolfgang Denk
2009-07-23 22:37 ` Jean-Christophe PLAGNIOL-VILLARD
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=4A66A86D.7070200@denx.de \
--to=hs@denx.de \
--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