public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: ayman at austin.rr.com <ayman@austin.rr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] pci memory booting on ppc460
Date: Wed, 23 Apr 2008 10:04:51 -0500	[thread overview]
Message-ID: <20080423150448.GA8998@crust.elkhashab.com> (raw)
In-Reply-To: <200804231026.51751.sr@denx.de>

On Wed, Apr 23, 2008 at 10:26:51AM +0200, Stefan Roese wrote:

> Full ACK from me. I would always recommend to use a small NOR FLASH with a 
> full-blown U-Boot for booting from NOR with full DDR2 setup etc. All this 
> will be hard to implement with all the restrictions for booting from PCI 
> (even though I have never done this before, but I suspect that it will be 
> quite as limited as booting from NAND).
> 
> > But of course there may be 
> > reasons to want to boot over PCI ...
> 
> Yes, what is the main reason you want to do this? As mentioned above, I 
> recommend to boot from a small NOR FLASH (512kB) and "wait" in U-Boot for the 
> PCI host to provide the OS/application image via PCI.

Ok, here is what I want to do.  I have a board that has several PPC460s
on it.  Each has its own DDR2.  One of them is the master and boots up
normally today with uboot, launches linux, etc.  What I want to do is
have that master load the flash binary image into memory and then lock
that memory down (via whatever kernel calls are required).  Then I want
to configure each slaves PCI bar registers to be able to read from this
main memory and then tell them to go.  So my thought was that it would
appear to the slaves that they are just loading from a regular flash
and this image would contain uboot, kernel, root filesystem.  Basically
everything a flash normally would have.  It sounded reasonable at the
time.   The reason to avoid a flash on every one is so that we don't
have to reflash that many CPUs every time and because it will take up
more board space.  Thanks 

- ame

  reply	other threads:[~2008-04-23 15:04 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 [this message]
2008-04-23 16:18           ` David Hawkins
2008-04-24  5:51             ` Stefan Roese
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=20080423150448.GA8998@crust.elkhashab.com \
    --to=ayman@austin.rr.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