From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please increase the image size for km boards
Date: Fri, 24 Oct 2014 08:57:44 +0200 [thread overview]
Message-ID: <5449F868.7050400@keymile.com> (raw)
In-Reply-To: <54491B20.5020608@freescale.com>
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
prev parent reply other threads:[~2014-10-24 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=5449F868.7050400@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=u-boot@lists.denx.de \
/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