linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
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 10:38:38 -0700	[thread overview]
Message-ID: <fa686aa40712050938j2d286655o94534a00131872e2@mail.gmail.com> (raw)
In-Reply-To: <1196875970.8544.12.camel@ld0161-tx32>

On 12/5/07, Jon Loeliger <jdl@freescale.com> wrote:
>
> The addition of the aliases node is needed for U-Boot
> and, eventually, cuImage, to help locate the proper
> nodes reliably when using the libfdt approach.
>
> Signed-off-by: Jon Loeliger <jdl@freescale.com>
> ---
>  arch/powerpc/boot/dts/mpc8641_hpcn.dts |   28 ++++++++++++++++++++--------
>  1 files changed, 20 insertions(+), 8 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/mpc8641_hpcn.dts b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> index abb26dc..b039f21 100644
> --- a/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> +++ b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> @@ -16,6 +16,17 @@
>         #address-cells = <1>;
>         #size-cells = <1>;
>
> +       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?

> +
>         cpus {
>                 #address-cells = <1>;
>                 #size-cells = <0>;
> @@ -107,7 +118,7 @@
>                         };
>                 };
>
> -               ethernet@24000 {
> +               enet0: ethernet@24000 {
>                         #address-cells = <1>;
>                         #size-cells = <0>;
>                         device_type = "network";
> @@ -127,7 +138,7 @@
>                         phy-connection-type = "rgmii-id";
>                 };
>
> -               ethernet@25000 {
> +               enet1: ethernet@25000 {
>                         #address-cells = <1>;
>                         #size-cells = <0>;
>                         device_type = "network";
> @@ -147,7 +158,7 @@
>                         phy-connection-type = "rgmii-id";
>                 };
>
> -               ethernet@26000 {
> +               enet2: ethernet@26000 {
>                         #address-cells = <1>;
>                         #size-cells = <0>;
>                         device_type = "network";
> @@ -167,7 +178,7 @@
>                         phy-connection-type = "rgmii-id";
>                 };
>
> -               ethernet@27000 {
> +               enet3: ethernet@27000 {
>                         #address-cells = <1>;
>                         #size-cells = <0>;
>                         device_type = "network";
> @@ -186,7 +197,8 @@
>                         phy-handle = <&phy3>;
>                         phy-connection-type = "rgmii-id";
>                 };
> -               serial@4500 {
> +
> +               serial0: serial@4500 {
>                         device_type = "serial";
>                         compatible = "ns16550";
>                         reg = <4500 100>;
> @@ -195,7 +207,7 @@
>                         interrupt-parent = <&mpic>;
>                 };
>
> -               serial@4600 {
> +               serial1: serial@4600 {
>                         device_type = "serial";
>                         compatible = "ns16550";
>                         reg = <4600 100>;
> @@ -222,7 +234,7 @@
>                 };
>         };
>
> -       pcie@f8008000 {
> +       pci0: pcie@f8008000 {
>                 compatible = "fsl,mpc8641-pcie";
>                 device_type = "pci";
>                 #interrupt-cells = <1>;
> @@ -430,7 +442,7 @@
>
>         };
>
> -       pcie@f8009000 {
> +       pci1: pcie@f8009000 {
>                 compatible = "fsl,mpc8641-pcie";
>                 device_type = "pci";
>                 #interrupt-cells = <1>;
> --
> 1.5.2.1.126.g6abd0
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-12-05 17:39 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 [this message]
2007-12-05 18:05   ` Jon Loeliger
2007-12-05 18:15     ` Grant Likely
2007-12-05 18:31     ` Josh Boyer
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=fa686aa40712050938j2d286655o94534a00131872e2@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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).