From: "Gerhard Pircher" <gerhard_pircher@gmx•net>
To: "Mark A. Greer" <mgreer@mvista•com>
Cc: linuxppc-dev@ozlabs•org, "list <linuxppc-dev"@ozlabs.org
Subject: Re: [RFC] Device tree for new desktop platform in arch/powerpc
Date: Mon, 18 Jun 2007 21:43:59 +0200 [thread overview]
Message-ID: <20070618194359.321010@gmx.net> (raw)
In-Reply-To: <20070618191529.GC8740@mag.az.mvista.com>
-------- Original-Nachricht --------
Datum: Mon, 18 Jun 2007 12:15:29 -0700
Von: "Mark A. Greer" <mgreer@mvista•com>
An: Gerhard Pircher <gerhard_pircher@gmx•net>
CC: linuxppc-dev@ozlabs•org, "list <linuxppc-dev"@ozlabs.org
Betreff: Re: [RFC] Device tree for new desktop platform in arch/powerpc
> 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?
> > If so, where should I specify the register address ranges (reg
> > property)? In the PCI device node or in the ISA device nodes,
> > as it is now?
>
> Each device's node should have a reg property for its registers.
> You'll need a ranges property for the pci-isa bridge as well.
Ah yes, didn't think about that.
> P.S. You should change email clients of fix the one you're using
> to break lines up so they don't wrap in a std 80 char line
> window.
Yeah, sorry. Forgot about that when writing the mail.
Gerhard
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
next prev parent reply other threads:[~2007-06-18 19:44 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 [this message]
2007-06-18 20:25 ` Mark A. Greer
2007-06-19 5:08 ` David Gibson
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=20070618194359.321010@gmx.net \
--to=gerhard_pircher@gmx$(echo .)net \
--cc="list <linuxppc-dev"@ozlabs.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mgreer@mvista$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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