From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Add aliases node to 8641hpcn DTS file.
Date: Wed, 5 Dec 2007 12:31:19 -0600 [thread overview]
Message-ID: <20071205123119.22c70455@zod.rchland.ibm.com> (raw)
In-Reply-To: <1196877907.8544.15.camel@ld0161-tx32>
On Wed, 05 Dec 2007 12:05:07 -0600
Jon Loeliger <jdl@freescale.com> wrote:
> On Wed, 2007-12-05 at 11:38, Grant Likely wrote:
>
> > >
> > > + aliases {
> > > + ethernet0 = &enet0;
> > > + ethernet1 = &enet1;
> > > + ethernet2 = &enet2;
> > > + ethernet3 = &enet3;
> > > + serial0 = &serial0;
> > > + serial1 = &serial1;
> > > + pci0 = &pci0;
> > > + pci1 = &pci1;
> > > + };
> >
> > I had thought aliases were supposed to be full paths to nodes instead
> > of phandles. Was I wrong?
>
> Indeed, that is correct. And they are!
>
> => fdt addr c00000
> => fdt print /aliases
> aliases {
> ethernet0 = "/soc8641@f8000000/ethernet@24000";
> ethernet1 = "/soc8641@f8000000/ethernet@25000";
> ethernet2 = "/soc8641@f8000000/ethernet@26000";
> ethernet3 = "/soc8641@f8000000/ethernet@27000";
> serial0 = "/soc8641@f8000000/serial@4500";
> serial1 = "/soc8641@f8000000/serial@4600";
> pci0 = "/pcie@f8008000";
> pci1 = "/pcie@f8009000";
> };
> => bootm 1000000 - c00000
>
> Grant, you need to keep up, man. Just this morning
> I pushed Gibson's patch to DTC to support this. :-)
So now the in-kernel version of DTC needs to support this.
josh
next prev parent reply other threads:[~2007-12-05 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 17:32 [PATCH] Add aliases node to 8641hpcn DTS file Jon Loeliger
2007-12-05 17:38 ` Grant Likely
2007-12-05 18:05 ` Jon Loeliger
2007-12-05 18:15 ` Grant Likely
2007-12-05 18:31 ` Josh Boyer [this message]
2007-12-05 18:05 ` Vitaly Bordug
2007-12-05 22:28 ` Mark A. Greer
2007-12-05 22:33 ` David Gibson
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=20071205123119.22c70455@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=jdl@freescale.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).