From: Jon Loeliger <jdl@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: [PATCH 1/3 v3] Add StorCenter DTS first draft.
Date: Tue, 22 Jan 2008 16:54:46 -0600 [thread overview]
Message-ID: <47967436.9070704@freescale.com> (raw)
In-Reply-To: <fa686aa40801221449p28889ea5r68bd726726558dc0@mail.gmail.com>
Grant Likely wrote:
> On 1/22/08, Jon Loeliger <jdl@jdl.com> wrote:
>> Based on the Kurobox DTS files.
>>
>> Signed-off-by: Andy Wilcox <andy@protium.com>
>> Signed-off-by: Jon Loeliger <jdl@jdl.com>
>
> Comments below
>
>> +
>> +/ {
>> + model = "StorCenter";
>> + compatible = "storcenter";
>
> Be specific! "iomega,storcenter". Even better if you put in the model number.
As I mentioned vefore, there is no further model number.
That _is_ the model name.
>> +
>> + soc@fc000000 {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + device_type = "soc";
>
> device_type should be dropped (but I know that requires changes to the
> existing mpc82xx support code).
And when the code is fixed, we can fix the DTS too... :-)
>> + compatible = "fsl,mpc8241", "mpc10x";
>
> fsl,mpc8241-immr would be better; this node describes the internally
> memory mapped registers; not the entire soc.
Uh, whatever? :-) 'Cuz how many other DTS files say that?
>> +
>> + mpic: interrupt-controller@40000 {
>> + #interrupt-cells = <2>;
>> + #address-cells = <0>;
>
> Is #address-cells needed? There are no child nodes.
I thought so. Could be wrong.
>> + chosen {
>> + linux,stdout-path = "/soc/serial@4500";
>
> /soc@fc000000/ perhaps?
Not really necessary to specify the unit number.
jdl
next prev parent reply other threads:[~2008-01-22 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 22:37 [PATCH 1/3 v3] Add StorCenter DTS first draft Jon Loeliger
2008-01-22 22:49 ` Grant Likely
2008-01-22 22:54 ` Jon Loeliger [this message]
2008-01-22 23:16 ` Grant Likely
2008-01-23 0:33 ` Benjamin Herrenschmidt
2008-01-23 0:47 ` Scott Wood
2008-01-23 1:39 ` Josh Boyer
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=47967436.9070704@freescale.com \
--to=jdl@freescale.com \
--cc=grant.likely@secretlab.ca \
--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).