* [U-Boot] Please increase the image size for km boards @ 2014-09-30 15:48 York Sun 2014-10-01 15:39 ` Valentin Longchamp 0 siblings, 1 reply; 6+ messages in thread From: York Sun @ 2014-09-30 15:48 UTC (permalink / raw) To: u-boot 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). Thanks, York ^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Please increase the image size for km boards 2014-09-30 15:48 [U-Boot] Please increase the image size for km boards York Sun @ 2014-10-01 15:39 ` Valentin Longchamp 2014-10-01 15:41 ` York Sun 0 siblings, 1 reply; 6+ messages in thread From: Valentin Longchamp @ 2014-10-01 15:39 UTC (permalink / raw) To: u-boot 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. Valentin ^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Please increase the image size for km boards 2014-10-01 15:39 ` Valentin Longchamp @ 2014-10-01 15:41 ` York Sun 2014-10-23 15:02 ` Valentin Longchamp 0 siblings, 1 reply; 6+ messages in thread From: York Sun @ 2014-10-01 15:41 UTC (permalink / raw) To: u-boot 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. York ^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Please increase the image size for km boards 2014-10-01 15:41 ` York Sun @ 2014-10-23 15:02 ` Valentin Longchamp 2014-10-23 15:13 ` York Sun 0 siblings, 1 reply; 6+ messages in thread From: Valentin Longchamp @ 2014-10-23 15:02 UTC (permalink / raw) To: u-boot 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. 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 ? Thank you very much Valentin ^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Please increase the image size for km boards 2014-10-23 15:02 ` Valentin Longchamp @ 2014-10-23 15:13 ` York Sun 2014-10-24 6:57 ` Valentin Longchamp 0 siblings, 1 reply; 6+ messages in thread From: York Sun @ 2014-10-23 15:13 UTC (permalink / raw) To: u-boot 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Please increase the image size for km boards 2014-10-23 15:13 ` York Sun @ 2014-10-24 6:57 ` Valentin Longchamp 0 siblings, 0 replies; 6+ messages in thread From: Valentin Longchamp @ 2014-10-24 6:57 UTC (permalink / raw) To: u-boot On 10/23/2014 05:13 PM, York Sun wrote: > 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. > No we don't. SPI NOR Flash is the only boot flash supported on this design. So I think the above changes should be enough. I will give them a try and send the patch when tested. Valentin ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-10-24 6:57 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-09-30 15:48 [U-Boot] Please increase the image size for km boards York Sun 2014-10-01 15:39 ` Valentin Longchamp 2014-10-01 15:41 ` York Sun 2014-10-23 15:02 ` Valentin Longchamp 2014-10-23 15:13 ` York Sun 2014-10-24 6:57 ` Valentin Longchamp
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox