linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
	Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: purpose of /chosen node (was RE: [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTSfiles)
Date: Fri, 16 Feb 2007 20:54:37 +1100	[thread overview]
Message-ID: <1171619678.5644.69.camel@localhost.localdomain> (raw)
In-Reply-To: <9415c89211d2197807813b8311f3ebb1@kernel.crashing.org>

On Fri, 2007-02-16 at 08:30 +0100, Segher Boessenkool wrote:
> > If the kernel needs a convenient place to keep a phandle to the
> > top level interrupt controller,
> 
> Well that's the first point: the kernel doesn't need this
> at all, it can derive this from the rest of the tree easy
> enough.

Not that easy. I beleive it's better to have it expressed explicitely.

> > how about just under root?
> 
> CHRP does this (in an extra-plus nasty way).
> 
> > (Or, we could make up a new node)
> 
> Duplicate node?  No way.  You can be flexible with adding
> extra properties, but every node should represent a (pseudo-)
> device, and every device in the system should be represented
> by exactly one node.
> 
> Or you could make the convention that /aliases/interrupt-controller
> points to the root interrupt controller, if you really
> think you want this.

That too.

Ben.

  reply	other threads:[~2007-02-16  9:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 16:47 [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTS files Timur Tabi
2007-02-13 17:16 ` Kumar Gala
2007-02-13 17:20   ` Timur Tabi
2007-02-13 19:29   ` Timur Tabi
2007-02-15  1:42   ` Segher Boessenkool
2007-02-14  0:31 ` David Gibson
2007-02-14  5:18   ` Timur Tabi
2007-02-14  5:24     ` David Gibson
2007-02-14 14:05       ` Timur Tabi
2007-02-14 23:33         ` David Gibson
2007-02-14 23:47           ` Timur Tabi
2007-02-15  1:40           ` Segher Boessenkool
2007-02-15 21:26             ` purpose of /chosen node (was RE: [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTSfiles) Yoder Stuart-B08248
2007-02-15 21:39               ` Kumar Gala
2007-02-15 21:45                 ` Yoder Stuart-B08248
2007-02-16  7:38                   ` Segher Boessenkool
2007-02-16  7:34                 ` Segher Boessenkool
2007-02-15 23:01               ` David Gibson
2007-02-16  0:08                 ` Benjamin Herrenschmidt
2007-02-16 16:58                   ` purpose of /chosen node (was RE: [PATCH] powerpc: deleteboot-cpu " Yoder Stuart-B08248
2007-02-16 17:00                     ` Kumar Gala
2007-02-16  7:30               ` purpose of /chosen node (was RE: [PATCH] powerpc: delete boot-cpu " Segher Boessenkool
2007-02-16  9:54                 ` Benjamin Herrenschmidt [this message]
2007-02-15 16:18           ` [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTS files Timur Tabi

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=1171619678.5644.69.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.org \
    --cc=stuart.yoder@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).