From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] pci memory booting on ppc460
Date: Thu, 24 Apr 2008 09:39:46 -0700 [thread overview]
Message-ID: <4810B7D2.4050309@ovro.caltech.edu> (raw)
In-Reply-To: <20080424161043.GC7245@crust.elkhashab.com>
Hi Ame,
> So maybe I need to clarify some more. The PPC460 data sheet
> is not too clear on this yet. However, here are my thoughts
> on this. Lets just take the simple case as an example. We
> have a plurality of 460s where a single one is the master.
> Between the master and all the slaves is a PCI bridge. The
> slaves are hardwired to boot from pci bus memory -- according
> to the datasheet that is at a fixed address. So there does
> not appear to be any need to do anything to the slave upon
> power up.
Really? I didn't see a comment about the fixed address when
I parsed the data sheet. Where is that comment in
PP460EX_DS2063.pdf, rev 1.09 April 14, 2008?
> Now the master boots and then allocates a chunk
> of contiguous memory using a kernel driver or whatever is
> needed. The image is just whatever the flash image would
> normally contain (uboot + kernel + rootfs).
Or you could just have a u-boot image, and then use u-boot
to fetch the kernel and rootfs.
> The address of that chunk is then given to the pci bridge
> so that it can perform inbound translation from the address
> that the PPC slaves will use to the address where the image
> is physically located. Then the slaves are taken out of reset
> and begin reading "flash" across the pci bus which really goes
> through the bridge and is mapped to the DRAM on the master (or I
> guess it could be the flash on the master, but DRAM seemed
> easier since it is already running).
>
> Ok, so how many holes does this approach have?
This seems reasonable to me.
However, without the full users manual for the 460EX, and the
users manual for the pci bridge, I can't really comment more.
Cheers,
Dave
next prev parent reply other threads:[~2008-04-24 16:39 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
2008-04-24 15:53 ` David Hawkins
2008-04-24 16:10 ` Ayman M. El-Khashab
2008-04-24 16:39 ` David Hawkins [this message]
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=4810B7D2.4050309@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--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