From: Scott Wood <scottwood@freescale.com>
To: Hu Mingkai-B21284 <B21284@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: DTS - re-organize the SPI partitions property
Date: Wed, 11 Sep 2013 20:15:42 -0500 [thread overview]
Message-ID: <1378948542.12204.490.camel@snotra.buserror.net> (raw)
In-Reply-To: <CF6CBFBA8EBBB949B6E321556F6E15090A135F45@039-SN2MPN1-011.039d.mgd.msft.net>
On Tue, 2013-09-10 at 21:07 -0500, Hu Mingkai-B21284 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, September 11, 2013 7:33 AM
> > To: Hu Mingkai-B21284
> > Cc: linuxppc-dev@ozlabs.org
> > Subject: Re: [PATCH] powerpc/85xx: DTS - re-organize the SPI partitions
> > property
> >
> > What happens to exsting users whose flash is laid out the existing way,
> > when they upgrade to these device trees?
> >
>
> The SPI flash layout should be mapping the new device tree.
>
> If the existing device tree is used to deploy the SPI flash, the following issues
> must be run into as the commit message described:
>
> 1. Kernel images would be overlapped with U-Boot image.
> 2. Kernel images would be overlapped with FMAN ucode.
> 3. Saving environment variables will crash the kernel image.
Has the SPI U-Boot image always been larger than 512K for all these
platforms? Why, given that we're under 512K for other boot modes?
> > We really should not be putting partition layout info in the device tree
> > to begin with...
> >
> OK, I will remove the layout diagram in the commit message.
That's not what I meant. I meant that the dts should be describing
hardware, and this is the sort of trouble we run into when we deviate
from that. A better way would be to use the mtdparts command line
option. Even better would be some sort of on-flash partition table.
-Scott
next prev parent reply other threads:[~2013-09-12 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 8:05 [PATCH] powerpc/85xx: DTS - re-organize the SPI partitions property Mingkai Hu
2013-09-10 23:33 ` Scott Wood
2013-09-11 2:07 ` Hu Mingkai-B21284
2013-09-12 1:15 ` Scott Wood [this message]
2013-09-17 11:06 ` Hu Mingkai-B21284
2013-09-23 23:02 ` Scott Wood
2013-09-24 10:27 ` Hu Mingkai-B21284
2013-09-24 19:37 ` Scott Wood
2013-09-30 8:31 ` Hu Mingkai-B21284
2013-10-01 19:37 ` 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=1378948542.12204.490.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B21284@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