From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/3] [POWERPC] Kilauea DTS
Date: Thu, 11 Oct 2007 14:02:12 +0200 [thread overview]
Message-ID: <200710111402.12449.sr@denx.de> (raw)
In-Reply-To: <1192103498.5534.101.camel@localhost.localdomain>
On Thursday 11 October 2007, Josh Boyer wrote:
> On Thu, 2007-10-11 at 10:49 +0200, Stefan Roese wrote:
> > > > + PowerPC,405EX@0 {
> > > > + device_type = "cpu";
> > > > + reg = <0>;
> > > > + clock-frequency = <0>; /* Filled in by U-Boot */
> > >
> > > Filled in by U-Boot itself? Or by a cuboot wrapper? (which I can't
> > > find in the patches.)
> >
> > By U-Boot itself. I have a U-Boot patch in the queue to add device tree
> > support for 4xx. Therefor I don't plan adding a cuboot wrapper for
> > Kilauea.
>
> Very cool!
You can take a look at the kilauea-405ex branch of my 4xx custodian repository
for a latest development snapshort:
http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-ppc4xx.git;a=shortlog;h=kilauea-405ex
> > > > + interrupt-parent = <&UIC1>;
> > > > +
> > > > + nor_flash@0,0 {
> > >
> > > You have no ranges property for the ebc parent node. Is if filled in
> > > by U-Boot? If so, please add a comment because otherwise I don't see
> > > how this mapping will work.
> >
> > Yes, it's filled in by U-Boot too. I'll add a comment here.
>
> Ok.
>
> > > No chosen node?
> >
> > No. U-Boot will provide all needed information here.
>
> Does it provide it by creating the chosen node? Or by still using the
> bd_t method?
bd_t? What's that? ;)
Best regards,
Stefan
next prev parent reply other threads:[~2007-10-11 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 9:10 [PATCH 3/3] [POWERPC] Kilauea DTS Stefan Roese
2007-10-10 20:21 ` Josh Boyer
2007-10-11 8:49 ` Stefan Roese
2007-10-11 11:51 ` Josh Boyer
2007-10-11 12:02 ` Stefan Roese [this message]
2007-10-11 12:13 ` Josh Boyer
2007-10-11 12:22 ` Stefan Roese
2007-10-12 3:15 ` David Gibson
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=200710111402.12449.sr@denx.de \
--to=sr@denx.de \
--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.