public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (#2)
Date: Thu, 19 May 2005 09:46:43 +0200	[thread overview]
Message-ID: <200505190946.45219.arnd@arndb.de> (raw)
In-Reply-To: <1116478614.918.75.camel@gaston>

On Dunnersdag 19 Mai 2005 06:56, Benjamin Herrenschmidt wrote:

>   d) the /memory node(s)
>   Required properties:
> 
>     - name : has to be "chosen"

s/chosen/memory/

>   c) The /chosen node
> 
>     - linux,platform : This is your platform number as assigned by the
>       architecture maintainers

Does this mean you want a new platform number for every board type?
I would guess that it might be easier to extend the maple platform
to support all boards with ppc970 and similar CPUs (except the
pmac and pSeries ones), just like I would like to extend the BPA
platform for all Cell based systems.

>   This is all that is currently required. However, it is strongly
>   recommended that you expose PCI host bridges as documented in the
>   PCI binding to open firmware, and your interrupt tree as documented
>   in OF interrupt tree specification.

AFAICS, the pci device tree is currently required if you want to
use an IOMMU or if you want PCI-X or PCIe style devices with
extended PCI config space. I wouldn't be surprised if other 
functionality also depends on it.

	Arnd <><

  reply	other threads:[~2005-05-19  7:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  7:09 [U-Boot-Users] RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO Benjamin Herrenschmidt
2005-05-18  8:12 ` Marius Groeger
2005-05-18 23:11   ` Benjamin Herrenschmidt
2005-05-19  9:52     ` Marius Groeger
2005-05-19 10:22       ` Benjamin Herrenschmidt
2005-05-19 13:18         ` Wolfgang Denk
2005-05-19 19:37           ` Linas Vepstas
2005-05-19 20:18             ` Dan Malek
2005-05-19 22:33           ` Benjamin Herrenschmidt
2005-05-19 23:20             ` Wolfgang Denk
2005-05-19 23:42               ` Benjamin Herrenschmidt
2005-05-20  3:11             ` Benjamin Herrenschmidt
2005-05-20  7:11               ` Marius Groeger
2005-05-20  7:23                 ` David Gibson
2005-05-20  7:27                 ` Benjamin Herrenschmidt
2005-05-18 23:32   ` Benjamin Herrenschmidt
2005-05-19  4:56 ` [U-Boot-Users] RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (#2) Benjamin Herrenschmidt
2005-05-19  7:46   ` Arnd Bergmann [this message]
2005-05-19  8:09     ` [U-Boot-Users] " Benjamin Herrenschmidt
2005-05-19 16:24     ` Segher Boessenkool
2005-05-19 13:18   ` [U-Boot-Users] " Wolfgang Denk
2005-05-19 13:16     ` Pantelis Antoniou
2005-05-19 22:20     ` Benjamin Herrenschmidt
2005-05-19 23:14       ` Wolfgang Denk
2005-05-19 23:28         ` Benjamin Herrenschmidt
2005-05-20  6:44         ` Stefan Nickl
2005-05-20  3:51     ` Hollis Blanchard
2005-05-20  6:59       ` Wolfgang Denk
2005-05-20  4:24     ` Paul Mackerras
2005-05-20  4:28       ` Paul Mackerras
2005-05-20  4:26   ` [U-Boot-Users] " Hollis Blanchard
2005-05-20  5:04     ` Benjamin Herrenschmidt

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=200505190946.45219.arnd@arndb.de \
    --to=arnd@arndb.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