All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoder Stuart-B08248" <stuart.yoder@freescale.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: RE: purpose of /chosen node (was RE: [PATCH] powerpc: delete boot-cpu and chosen nodes from all DTSfiles)
Date: Thu, 15 Feb 2007 14:45:59 -0700	[thread overview]
Message-ID: <9696D7A991D0824DBA8DFAC74A9C5FA302A1BC91@az33exm25.fsl.freescale.net> (raw)
In-Reply-To: <B8882F02-616E-4E71-BECC-82BDE5D88A4E@kernel.crashing.org>

=20

> -----Original Message-----
> From: Kumar Gala [mailto:galak@kernel.crashing.org]=20
> Sent: Thursday, February 15, 2007 3:39 PM
> To: Yoder Stuart-B08248
> Cc: Segher Boessenkool; Benjamin Herrenschmidt;=20
> linuxppc-dev@ozlabs.org
> Subject: Re: purpose of /chosen node (was RE: [PATCH]=20
> powerpc: delete boot-cpu and chosen nodes from all DTSfiles)
>=20
>=20
> On Feb 15, 2007, at 3:26 PM, Yoder Stuart-B08248 wrote:
> >> -----Original Message-----
> >> From: linuxppc-dev-bounces+b08248=3Dfreescale.com@ozlabs.org
> >> [mailto:linuxppc-dev-bounces+b08248=3Dfreescale.com@ozlabs.org]
> >> On Behalf Of Segher Boessenkool
> >> Sent: Wednesday, February 14, 2007 7:40 PM
> >> To: David Gibson
> >> Cc: linuxppc-dev@ozlabs.org; Tabi Timur-B04825
> >> Subject: Re: [PATCH] powerpc: delete boot-cpu and chosen
> >> nodes from all DTSfiles
> >>
> >>> My point is that the interrupt-controller property in
> >> /chosen *should*
> >>> be there, but it doesn't make a lot of sense for it to be=20
> set by the
> >>> bootloader (because it's a fixed property of the board).
> >>
> >> And that means it shouldn't be in /chosen at all.  It's not
> >> just a fixed property of the board, it is a physical property
> >> of the board.  It doesn't belong in /chosen.
> >
> > I agree with Segher here.  The interrupt-controller property doesn't
> > belong in /chosen.
> >
> > The 1275 OF spec says about /chosen:
> >
> >    Has properties describing parameters chosen or specified at
> >    runtime.
>=20
> I want to reiterate something Paul mentioned, any similarity=20
> that the =20
> device tree has to 1275 is strictly coincidental.

I understand that point, but mixing the types of properties in
/chosen doesn't buy us anything.  We shouldn't be shackled by
the 1275 spec, but having nodes like /chosen with designated
purpose architecturally make sense.

/chosen shouldn't be a catch-all or a convenient place to stick
stuff.  I think in this case following 1275 is a good thing.

Stuart

  reply	other threads:[~2007-02-15 21:46 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 [this message]
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
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=9696D7A991D0824DBA8DFAC74A9C5FA302A1BC91@az33exm25.fsl.freescale.net \
    --to=stuart.yoder@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.