From: Hollis Blanchard <hollis@penguinppc.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Patch] Fix the mpc8641_hpcn.dts file.
Date: Thu, 17 Aug 2006 13:51:40 -0500 [thread overview]
Message-ID: <1155840700.27466.64.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <1155835482.10054.140.camel@cashmere.sps.mot.com>
Doesn't the device tree compiler add linux,phandle properties as needed?
In this case that would be when the node is referenced by a
"<&/foo/bar/i8259@4d0>" property.
On Thu, 2006-08-17 at 12:24 -0500, Jon Loeliger wrote:
> Add 'linux,phandle' entry to i8259@4d0 node.
>
> Signed-off-by: Zhang Wei <wei.zhang@freescale.com>
> Signed-off-by: Jon Loeliger <jdl@freescale.com>
> ---
>
> Paul,
>
> If possible, this should be slated for the
> upcoming .18 release.
>
> Thanks,
> jdl
>
>
> arch/powerpc/boot/dts/mpc8641_hpcn.dts | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/mpc8641_hpcn.dts b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> index e832a88..f0c7731 100644
> --- a/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> +++ b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> @@ -293,6 +293,7 @@
> f800 0 0 4 4d0 0 0
> >;
> i8259@4d0 {
> + linux,phandle = <4d0>;
> clock-frequency = <0>;
> interrupt-controller;
> device_type = "interrupt-controller";
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2006-08-17 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 17:24 Patch] Fix the mpc8641_hpcn.dts file Jon Loeliger
2006-08-17 18:51 ` Hollis Blanchard [this message]
2006-08-17 21:20 ` [PATCH] Directly reference i8259@4d0 nodes in mpc8641_hpcn.dts Jon Loeliger
2006-08-18 0:09 ` Benjamin Herrenschmidt
2006-08-18 0:43 ` Mark A. Greer
2006-08-18 1:59 ` Benjamin Herrenschmidt
2006-08-18 5:54 ` Zhang Wei-r63237
2006-08-18 7:21 ` Benjamin Herrenschmidt
2006-08-18 17:32 ` Jon Loeliger
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=1155840700.27466.64.camel@basalt.austin.ibm.com \
--to=hollis@penguinppc.org \
--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).