From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_MONITOR_BASE < CFG_FLASH_BASE
Date: Thu, 17 May 2007 09:55:56 -0500 [thread overview]
Message-ID: <464C6CFC.7020602@freescale.com> (raw)
In-Reply-To: <464B951E.206@ovro.caltech.edu>
David Hawkins wrote:
> The MPC8349E can be booted such that the core is held in
> reset, and the processor registers can be configured over
> PCI by another host computer. Therefore it is conceivable
> that the host can program the SDRAM controller on the
> MPC8349E and take the core out of reset. If the core
> is configured to boot from an address mapped to SDRAM,
> then U-Boot could have been copied to SDRAM by the
> host. Once U-Boot boots, it could then use FTP etc
> to boot the kernel blah blah ...
Ok fine, but you're talking about an 8349 on a different board. I have a *board* header
file for the MPC8349E-mITX, which comes with 16MB of flash and works just fine. I've done
the hard work of getting U-Boot running on that board with flash. So the question is, am
I going to upset someone if I remove support for booting from RAM on that board?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-17 14:55 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
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 [this message]
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=464C6CFC.7020602@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