From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Loeliger" <jdl@freescale.com>
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:16:35 -0700 [thread overview]
Message-ID: <fa686aa40801221516o27154589w20fabe3e365230c0@mail.gmail.com> (raw)
In-Reply-To: <47967436.9070704@freescale.com>
On 1/22/08, Jon Loeliger <jdl@freescale.com> wrote:
> 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.
/me has a short memory.
> >> + 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?
True, we haven't been doing this until recently; but we've also been
stumbling about over the last 2 years figuring out how best to use
this fancy device tree thing in embedded systems effectively. Best
practices are starting to emerge (wadda you know, the open firmware
recommended practices actually have good thought behind them) and
being specific with the compatible property is one aspect. I'm moving
the 5200 over to specifying -immr and some of the other soc ports are
doing so also. Chat with Scott Wood.
> >> + linux,stdout-path = "/soc/serial@4500";
> >
> > /soc@fc000000/ perhaps?
>
> Not really necessary to specify the unit number.
Okay, I wasn't sure if we could get away with that with the fdt.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-01-22 23:16 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
2008-01-22 23:16 ` Grant Likely [this message]
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=fa686aa40801221516o27154589w20fabe3e365230c0@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jdl@freescale.com \
--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).