From: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
To: Scott Wood <scottwood@freescale.com>
Cc: stef.van.os@prodrive-technologies.com,
Martijn de Gouw <martijn.de.gouw@prodrive.nl>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: Add OCA4080 board support
Date: Tue, 15 Apr 2014 13:24:38 +0200 [thread overview]
Message-ID: <534D16F6.9090305@prodrive-technologies.com> (raw)
In-Reply-To: <1397514507.20280.223.camel@snotra.buserror.net>
On 04/15/2014 12:28 AM, Scott Wood wrote:
> On Mon, 2014-04-14 at 14:35 +0200, Martijn de Gouw wrote:
>> + lbc: localbus@ffe124000 {
>> + reg = <0xf 0xfe124000 0 0x1000>;
>> + ranges = <0 0 0xf 0xef800000 0x800000>;
>> +
>> + flash@0,0 {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + compatible = "cfi-flash";
>> + reg = <0 0 0x00800000>;
>> + bank-width = <2>;
>> + device-width = <2>;
>> + partition@rcw {
>> + label = "rcw";
>> + reg = <0x00000000 0x00020000>;
>> + };
>> + partition@fman-ucode {
>> + label = "fman-ucode";
>> + reg = <0x00020000 0x00020000>;
>> + };
>> + partition@user {
>> + label = "user";
>> + reg = <0x00040000 0x00680000>;
>> + };
>> + partition@env0 {
>> + label = "env0";
>> + reg = <0x006c0000 0x00020000>;
>> + };
>> + partition@env1 {
>> + label = "env1";
>> + reg = <0x006e0000 0x00020000>;
>> + };
>> + partition@u-boot {
>> + label = "u-boot";
>> + reg = <0x00700000 0x00080000>;
>> + };
>> + partition@u-boot-backup {
>> + label = "u-boot-backup";
>> + reg = <0x00780000 0x00080000>;
>> + };
>
> These are not valid unit addresses. Regardless, please don't put
> partition info in the dts.
How is this different than the partitions defined in i.e. p4080ds.dts?
Of course I can remove them from the dts, but where should they be defined?
--
Martijn de Gouw
Engineer
Prodrive Technologies B.V.
Mobile: +31 63 17 76 161
Phone: +31 40 26 76 200
next prev parent reply other threads:[~2014-04-15 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 12:35 [PATCH] powerpc/85xx: Add OCA4080 board support Martijn de Gouw
2014-04-14 22:28 ` Scott Wood
2014-04-15 11:24 ` Martijn de Gouw [this message]
2014-04-15 17:15 ` Scott Wood
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=534D16F6.9090305@prodrive-technologies.com \
--to=martijn.de.gouw@prodrive-technologies.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martijn.de.gouw@prodrive.nl \
--cc=scottwood@freescale.com \
--cc=stef.van.os@prodrive-technologies.com \
/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).