On 10/23/2014 08:02 AM, Valentin Longchamp wrote: > Hi York, > > On 10/01/2014 05:41 PM, York Sun wrote: >> On 10/01/2014 08:39 AM, Valentin Longchamp wrote: >>> Hi York, >>> >>> On 09/30/2014 05:48 PM, York Sun wrote: >>>> Valentin, >>>> >>>> We are seeing the image size of kmcoge4 and kmlion1 are on the edge. >>>> Attempts to >>>> add new features cause overflow. Would you consider to increase the image >>>> size >>>> for km boards. You may have noticed several patches doing this for selected >>>> boards (search git log for 768K). >>>> >>> >>> I am going to have a look at it and see what the impact is for us. >>> Basically I >>> have nothing against changing this value, especially for kmcoge4/kmlion1. >>> >> >> Thanks. I can anticipate some chaos on the flash memory map. The >> environmental >> variables are stored before u-boot in flash, if FMan ucode if the SoC >> requires it. >> > > I have finally had time to look at this point. For kmcoge4, we are lucky to > have > enough space on our boot SPI Flash and I had reserved 1M for u-boot when doing > the layout to have some reserve. So in my case I am avoiding the possible > flash > memory map chaos. > > If I have understood correctly, for the powerpc boards, the default value was > changed from 512K to 768K. What do you think makes more sense, stay on line > with > the other powerpc boards with 768K or go directly to 1M since this space is > avaible ? I prefer to stay on line.
I agree. > > Another question: am I right that the two things that need to be adjusted are: > - CONFIG_SYS_TEXT_BASE > - CONFIG_SYS_MONITOR_LEN > > or am I missing something ? > You don't have other than NOR flash boot, do you? If yes, you need to take care of them, too. You can find some example by looking into git log, search for 768K. York _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
