From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Li Yang <leoli@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 11/12] Add MPC8360EMDS default dts file
Date: Thu, 28 Sep 2006 17:38:16 +0400 [thread overview]
Message-ID: <20060928173816.168d4cc2@vitb.ru.mvista.com> (raw)
In-Reply-To: <451B8592.7040609@freescale.com>
On Thu, 28 Sep 2006 16:19:30 +0800
Li Yang <leoli@freescale.com> wrote:
> + muram@10000 {
> + device_type = "muram";
> + ranges = <0 00010000 0000c000>;
> +
> + data-only@0{
> + reg = <0 c000>;
> + };
> + };
> +
Why not to have reg property, showing the allocation ranges? data-only seems redundant as a node...
> +
> + brg@640 {
> + device_type = "brg";
> + reg = <668 4>;
> + };
> +
I am recalling brg's removed from the dts before, since spec is silent guess we do not need it for now.
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2006-09-28 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 8:19 [PATCH 11/12] Add MPC8360EMDS default dts file Li Yang
2006-09-28 13:38 ` Vitaly Bordug [this message]
2006-09-29 7:46 ` Li Yang-r58472
2006-09-29 12:50 ` Vitaly Bordug
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=20060928173816.168d4cc2@vitb.ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).