[PATCH] powerpc/85xx: DTS - re-organize the SPI partitions property

Scott Wood scottwood at freescale.com
Thu Sep 12 11:15:42 EST 2013


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 at 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





More information about the Linuxppc-dev mailing list