From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add StorCenter DTS first draft.
Date: Tue, 17 Jul 2007 16:57:27 +0200 [thread overview]
Message-ID: <630B6BC9-389F-4F5C-AE8F-9C3131C4543E@kernel.crashing.org> (raw)
In-Reply-To: <E1IAnwC-0003Xm-6U@jdl.com>
> Comments welcome, of course.
Well you asked for it :-)
> +/ {
> + model = "StorCenter";
If you can find a real model number, put it in here,
instead.
> + compatible = "storcenter";
Needs a manufacturer name in there.
> + PowerPC,603e { /* Really 8241 */
So say "PowerPC,8241@0", or "PowerPC,e300@0" (or whatever
the CPU core in there is), or simply "cpu@0", following
the generic naming recommended practice.
> + bus-frequency = <0>;
Is this filled in anywhere? Please document that, if so.
> + /* Following required by dtc but not used */
> + i-cache-line-size = <0>;
> + d-cache-line-size = <0>;
> + i-cache-size = <4000>;
> + d-cache-size = <4000>;
Not used _by the Linux kernel_, it's required by the
PowerPC binding. Perhaps that should be modified
for flat device tree use, there are many more required
properties that no flat tree has anyway.
> + flash@ff800000 {
> + device_type = "rom";
I'm sure you know I find this "rom" binding to be crap.
However, I didn't yet write up the "cfi" binding, so I
can't complain ;-)
> + partitions = <
> + 00000000 0000E000
> + 0000E000 00002000
> + 00010000 00040000
> + 00050000 00200000
> + 00250000 004B0000
> + 00700000 00020000
> + 00720000 00010000
> + 00730000 00010000
> + 00740000 000B0000
> + >;
Nothing from 7f0000 to 7fffff?
> + soc10x {
Bad name. Where is the binding for this? I don't think
I saw it before.
> + compatible = "mpc10x";
"manufacturer,106-host" or similar. But this isn't an 10x
at all, is it?
> + store-gathering = <0>; /* 0 == off, !0 == on */
Don't define this as "!0", but as "1".
> + i2c@fdf03000 {
> + device_type = "i2c";
No device_type, there is no I2C binding.
> + compatible = "fsl-i2c";
Needs to be more specific.
> + mpic: pic@fdf40000 {
interrupt-controller@fdf40000
> + #interrupt-cells = <2>;
> + #address-cells = <0>;
No #address-cells here.
> + device_type = "open-pic";
device_type = "interrupt-controller" I believe, unless
the mpic binding does something weird.
> + pci@fe800000 {
> + clock-frequency = <d# 100000000>; /* Hz */
100MHz PCI? Interesting.
> + interrupt-map = <
> + /* IDSEL 0x15 - ETH */
> + 7800 0 0 1 &mpic 0 1
7800 isn't device 0x15. I think you meant 15.
Segher
next prev parent reply other threads:[~2007-07-17 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 14:22 [PATCH] Add StorCenter DTS first draft Jon Loeliger
2007-07-17 14:57 ` Segher Boessenkool [this message]
2007-07-17 16:26 ` Josh Boyer
2007-07-17 16:38 ` Segher Boessenkool
2007-07-17 22:27 ` Jon Loeliger
2007-07-17 22:34 ` Scott Wood
2007-07-17 22:56 ` Jon Loeliger
2007-07-18 16:19 ` Segher Boessenkool
2007-07-18 18:27 ` Kumar Gala
2007-07-19 17:03 ` Segher Boessenkool
2007-07-18 1:39 ` Benjamin Herrenschmidt
2007-07-18 16:13 ` Segher Boessenkool
2007-07-18 21:54 ` Benjamin Herrenschmidt
2007-07-19 16:05 ` Jon Loeliger
2007-07-19 17:07 ` Segher Boessenkool
2007-07-19 21:39 ` Benjamin Herrenschmidt
2007-07-20 7:14 ` 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=630B6BC9-389F-4F5C-AE8F-9C3131C4543E@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=jdl@jdl.com \
--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 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).