From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Small fixes for the Ebony device tree
Date: Tue, 15 May 2007 11:17:04 +1000 [thread overview]
Message-ID: <20070515011704.GB565@localhost.localdomain> (raw)
In-Reply-To: <3af16d1a6c09901f10dca3b6a3f8c698@kernel.crashing.org>
On Mon, May 14, 2007 at 02:59:31PM +0200, Segher Boessenkool wrote:
> > - i-cache-size = <0>;
> > - d-cache-size = <0>;
> > + i-cache-size = <2000000>; /* 32 kB */
> > + d-cache-size = <2000000>; /* 32 kB */
>
> That's 32MB, not 32kB. Better fix this :-)
Duh. Fixed.
> > UIC0: interrupt-controller0 {
>
> > UIC1: interrupt-controller1 {
>
> It's a shame you can't use unit addresses for these since
> you use "dcr-reg" instead of "reg". Oh well.
>
> > SDRAM0: sdram {
> > - device_type = "memory-controller";
> > compatible = "ibm,sdram-440gp", "ibm,sdram";
>
> Maybe rename the node to "memory-controller"?
Hmm, yeah, I guess so.
> > + SRAM0: sram {
> > + compatible = "ibm,sram440gp";
> > + dcr-reg = <020 8 00a 1>;
> > + };
>
> Is this thing _only_ addressable over DCRs? Weird.
Well... the control registers are certainly DCR only. I guess there's
the actual SRAM itself, though whether this belongs in this node, or
elsewhere isn't immediately clear. I haven't yet investigated how the
SRAM is mapped (it depends on DIP switch settings) so I'm certainly
not considering this node complete yet.
> > MAL0: mcmal {
> > - device_type = "mcmal-dma";
> > + device_type = "dma-controller";
> > compatible = "ibm,mcmal-440gp", "ibm,mcmal";
>
> Remove "device_type", change name to "dma-controller"?
Don't really want to remove the device_type, because the MAL driver
looks for it at present. Don't really want to change the name, since
that might encourage confusion with the other (more conventional) DMA
controller.
> > EBC0: ebc {
> > - device_type = "ibm,ebc";
> > compatible = "ibm,ebc-440gp";
>
> You forgot "ibm,ebc" here.
Hmm.. yeah, I guess.
Revised patch coming shortly.
--
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-05-15 1:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 4:54 Small fixes for the Ebony device tree David Gibson
2007-05-14 12:22 ` Josh Boyer
2007-05-14 12:59 ` Segher Boessenkool
2007-05-14 15:09 ` Josh Boyer
2007-05-15 1:17 ` David Gibson [this message]
2007-05-15 4:59 ` Segher Boessenkool
2007-05-15 5:46 ` David Gibson
2007-05-16 3:47 ` David Gibson
2007-05-15 18:15 ` Mark A. Greer
-- strict thread matches above, loose matches on Subject: below --
2007-05-15 2:00 David Gibson
2007-05-15 5:11 ` Segher Boessenkool
2007-05-15 5:47 ` David Gibson
2007-05-15 6:11 ` Stefan Roese
2007-05-15 6:18 ` David Gibson
2007-05-15 6:28 ` Segher Boessenkool
2007-05-15 6:34 ` David Gibson
2007-05-15 6:47 ` Segher Boessenkool
2007-05-15 6:58 ` David Gibson
2007-05-15 7:07 ` Segher Boessenkool
2007-05-16 3:47 ` David Gibson
2007-05-15 6:46 ` Stefan Roese
2007-05-15 7:02 ` Segher Boessenkool
2007-05-16 3:48 David Gibson
2007-05-16 13:35 ` Segher Boessenkool
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=20070515011704.GB565@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 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).