From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] pci memory booting on ppc460
Date: Thu, 24 Apr 2008 07:51:42 +0200 [thread overview]
Message-ID: <200804240751.42742.sr@denx.de> (raw)
In-Reply-To: <480F6147.4060406@ovro.caltech.edu>
On Wednesday 23 April 2008, David Hawkins wrote:
> Here's a few ideas then.
>
> 1) Use the main host to setup DDR on each of the targets,
> copy a U-Boot image to each target, and then enable the
> targets to boot from DDR.
I don't see how this could be done. The SDRAM has to be setup by the CPU
itself and can't be setup via another PCI host.
> The target U-Boot versions would have to skip all DDR
> initialization, since they are running from DDR.
>
> I believe this code would come under ...
>
> http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarte
>dInRAM
>
> Which contains the warning:
>
> 'But it is difficult, unsupported, and fraught with peril.'
>
> Wolfgang and Stephan could probably comment more on this.
>
> 2) Configure an inbound translation window on the host to point
> a PCI window to its *flash*.
>
> Configure the outbound translation windows on the targets to
> point to the host inbound window.
This is probably only possible from the CPU itself too. And where should the
code come from to do this?
> Each target would then boot from the same flash as the host.
> Assuming there was some I/O to distinguish the targets from the
> host, the code could determine what to do at runtime.
>
> This has the disadvantage that all boards are booting from
> potentially slower flash memory, but that may not matter.
>
> 3) Configure the host DDR memory such that the OS does not use
> all installed memory, eg. reserves enough memory for a U-Boot
> image.
>
> Setup the host inbound translation window to point to that
> linear DDR region, and have the host copy the image there.
>
> Setup the targets as in (2) and let them boot.
>
> The nice thing about (2) and (3) is that the target processors are
> effectively in the 'virgin' state that flash booting expects, so
> the modifications to U-Boot required to support the booting scheme
> would be minimal.
I don't think this is possible. To configure the translation windows, code is
needed on all PPC's.
> 4) Another option would be to place SRAM on each of the other
> processors, and copy the U-Boot image there. That way flash
> on the targets is replaced with SRAM.
>
> However, this would require a hardware change, and is not
> much of an improvement.
SRAM or FLASH, no big difference here. The only advantage is that there is no
need to update all target FLASH's.
Another idea would be to put only one NOR FLASH for all target PPC's on the
board. Then you "release" (put out of reset) all target PPC's from the host
PPC in a sequential order. This way there should be no problem sharing the
NOR FLASH.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-04-24 5:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:11 [U-Boot-Users] pci memory booting on ppc460 ayman at austin.rr.com
2008-04-22 18:47 ` David Hawkins
2008-04-22 20:53 ` Wolfgang Denk
2008-04-22 21:17 ` David Hawkins
2008-04-23 8:26 ` Stefan Roese
2008-04-23 15:04 ` ayman at austin.rr.com
2008-04-23 16:18 ` David Hawkins
2008-04-24 5:51 ` Stefan Roese [this message]
2008-04-24 15:53 ` David Hawkins
2008-04-24 16:10 ` Ayman M. El-Khashab
2008-04-24 16:39 ` David Hawkins
2008-04-25 6:13 ` Stefan Roese
2008-04-25 12:41 ` Ayman El-Khashab
2008-04-25 12:45 ` Stefan Roese
2008-04-25 15:26 ` Ayman M. El-Khashab
2008-04-24 16:17 ` David Hawkins
2008-04-25 6:01 ` Stefan Roese
2008-04-25 16:25 ` David Hawkins
2008-04-22 19:45 ` 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=200804240751.42742.sr@denx.de \
--to=sr@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