From: David Gibson <david@gibson.dropbear.id.au>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: "list <linuxppc-dev"@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Tue, 19 Jun 2007 15:08:12 +1000 [thread overview]
Message-ID: <20070619050812.GA32039@localhost.localdomain> (raw)
In-Reply-To: <20070618202518.GG8740@mag.az.mvista.com>
On Mon, Jun 18, 2007 at 01:25:18PM -0700, Mark A. Greer wrote:
> On Mon, Jun 18, 2007 at 09:43:59PM +0200, Gerhard Pircher wrote:
> > Von: "Mark A. Greer" <mgreer@mvista.com>
> > > On Mon, Jun 18, 2007 at 08:57:15PM +0200, Gerhard Pircher wrote:
> > >
> > > > 1. The AmigaOne makes use of different G3...
> > >
> > > I'm far from an authoritative figure on this but making a
> > > reasonable default (in your dts file) then updating in the
> > > bootwrapper makes sense to me. That's what I did for several
> > > properties in the prpmc2800's dts.
> > So, the bootwrapper should update the name property of the CPU node. Is the cpu node name used somewhere?
>
> Oh, sorry I really talking about the cpu frequencies, etc.
> I don't think the name of the cpu node matters but I'd have to check.
> Others probably know off the top of their heads.
I don't believe the name is actually used. It would be nice to get it
right, though - I think it can be considered option for the first cut,
though.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-06-19 5:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 18:57 [RFC] Device tree for new desktop platform in arch/powerpc Gerhard Pircher
2007-06-18 19:15 ` Mark A. Greer
2007-06-18 19:43 ` Gerhard Pircher
2007-06-18 20:25 ` Mark A. Greer
2007-06-19 5:08 ` David Gibson [this message]
2007-06-19 5:42 ` David Gibson
2007-06-19 6:16 ` Segher Boessenkool
2007-06-19 8:40 ` Gerhard Pircher
2007-06-19 9:14 ` Segher Boessenkool
2007-06-19 9:52 ` Gerhard Pircher
2007-06-19 10:08 ` Segher Boessenkool
2007-06-19 12:37 ` Gerhard Pircher
2007-06-19 13:15 ` Segher Boessenkool
2007-06-19 13:29 ` Gerhard Pircher
2007-06-21 12:42 ` Benjamin Herrenschmidt
2007-06-21 13:28 ` Gerhard Pircher
2007-06-21 14:59 ` Segher Boessenkool
2007-06-21 14:29 ` Segher Boessenkool
2007-06-21 23:25 ` Benjamin Herrenschmidt
2007-06-22 7:52 ` Segher Boessenkool
2007-06-22 8:16 ` Benjamin Herrenschmidt
2007-06-22 9:10 ` Segher Boessenkool
2007-06-19 6:08 ` Segher Boessenkool
2007-06-19 9:08 ` Gerhard Pircher
2007-06-19 9:28 ` Segher Boessenkool
2007-06-21 12:36 ` Benjamin Herrenschmidt
2007-06-21 13:20 ` Gerhard Pircher
2007-06-21 14:38 ` Segher Boessenkool
2007-06-21 16:27 ` Gerhard Pircher
2007-06-21 23:22 ` Benjamin Herrenschmidt
2007-06-22 13:12 ` Gerhard Pircher
2007-06-22 13:40 ` Benjamin Herrenschmidt
2007-06-21 14:24 ` Segher Boessenkool
2007-06-21 16:21 ` Gerhard Pircher
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=20070619050812.GA32039@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc="list <linuxppc-dev"@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mgreer@mvista.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 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.