From: Bryan O'Donoghue <bodonoghue@codehermit.ie>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for Analogue & Micro ASP837E board
Date: Wed, 7 May 2008 00:30:37 +0100 [thread overview]
Message-ID: <20080507003037.2bec5820@neuromancer.mindspace> (raw)
In-Reply-To: <8D90346B-3E16-4B77-BFF0-35F1FAA1B2B8@kernel.crashing.org>
On Tue, 6 May 2008 08:37:16 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:
/;
> > +
> > +/ {
> > + model = "ASP8347E";
> > + compatible = "ASP8347E";
>
> "analogue-and-micro, ASP8347E";
Fair enough.
> > + memory {
> > + device_type = "memory";
> > + reg = <0x00000000 0x8000000>; // 128MB at 0
>
> is memory really fixed on this board or does the bootloader set this
> if, dynamic make it <0 0>
It's fixed as far as I know.
> > + soc8349@ff000000 {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + device_type = "soc";
> > + ranges = <0x0 0xff000000 0xff100000>;
>
> this is wrong, size should be like 0x100000
Agreed - typo !
> > + enet0: ethernet@24000 {
> > + cell-index = <0>;
> > + device_type = "network";
> > + model = "TSEC";
> > + compatible = "gianfar";
> > + reg = <0x24000 0x1000>;
> > + local-mac-address = [ 00 08 e5 11 32 33 ];
> > + interrupts = <32 0x8 33 0x8 34 0x8>;
> > + interrupt-parent = <&ipic>;
> > + phy-handle = <&phy0>;
> > + linux,network-index = <0>;
>
> you shouldn't need this anymore. we should be using the aliases.
Aliases sound good to me. Don't know too much about how this should be defined
in a dts though, do you have an example I could use as a base for reference ?
Cheers.
prev parent reply other threads:[~2008-05-06 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 2:28 [PATCH] Add support for Analogue & Micro ASP837E board Bryan O'Donoghue
2008-05-06 6:11 ` Stephen Rothwell
2008-05-06 10:30 ` Bryan O'Donoghue
2008-05-06 13:37 ` Kumar Gala
2008-05-06 23:30 ` Bryan O'Donoghue [this message]
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=20080507003037.2bec5820@neuromancer.mindspace \
--to=bodonoghue@codehermit.ie \
--cc=galak@kernel.crashing.org \
--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).