public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_MONITOR_BASE < CFG_FLASH_BASE
Date: Wed, 16 May 2007 17:11:27 -0500	[thread overview]
Message-ID: <464B818F.60509@freescale.com> (raw)
In-Reply-To: <20070516220434.ABD38352650@atlas.denx.de>

Wolfgang Denk wrote:
> In message <464B6DCC.4030203@freescale.com> you wrote:
>> On a system that has flash, why would we ever support this configuration?  It doesn't even 
>> make any sense, because a whole bunch of DDR and LAWBAR setup needs to happen before RAM 
>> can even be accessed, so you can't copy u-boot to RAM and reset the system.
> 
> Did you read the FAQ? You just wrote another version of "14.2.1. Can
> U-Boot be configured such that it can be started in RAM?"

Yes, I have read it, but it doesn't really answer my question.  I'm not asking if I can 
boot from RAM, I'm asking why would someone think it could be done?  If anything, 14.2.1 
re-inforces my point: if booting from RAM doesn't make sense, why are so many board header 
files configured to enable it?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-05-16 22:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 20:47 [U-Boot-Users] CFG_MONITOR_BASE < CFG_FLASH_BASE Timur Tabi
2007-05-16 22:04 ` Wolfgang Denk
2007-05-16 22:11   ` Timur Tabi [this message]
2007-05-16 23:04     ` Leonid
2007-05-16 23:11       ` Timur Tabi
2007-05-17  2:12         ` Leonid
2007-05-17 15:35         ` Jon Loeliger
2007-05-17  0:11       ` Wolfgang Denk
2007-05-17  1:47         ` Leonid
2007-05-17 10:00           ` Wolfgang Denk
2007-05-16 23:34     ` David Hawkins
2007-05-17 14:55       ` Timur Tabi
2007-05-17 15:55         ` David Hawkins
2007-05-17 20:29         ` Wolfgang Denk
2007-08-16 11:31       ` Florian Boelstler
2007-08-16 11:51         ` Wolfgang Denk
2007-05-17  0:08     ` Wolfgang Denk

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=464B818F.60509@freescale.com \
    --to=timur@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