public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] powerpc/mpc85xx: Increase image size
Date: Wed, 16 Oct 2013 10:41:40 -0700	[thread overview]
Message-ID: <525ECFD4.4080704@freescale.com> (raw)
In-Reply-To: <525849F0.60002@freescale.com>

On 10/11/2013 11:56 AM, York Sun wrote:
> On 10/11/2013 11:39 AM, Scott Wood wrote:
>> On Fri, 2013-10-11 at 11:29 -0700, York Sun wrote:
>>> Scott, et al.
>>>
>>> I'd like to start the discussion to increase u-boot image size for some
>>> mpc85xx targets. As we all know the reset vector is at the very end and
>>> linking process start from the top. This gives us no good choice but to
>>> use fixed image size. While we have more and more features, the size
>>> increases inevitably. It's time to adjust the arbitrary size. We are now
>>> using 512KB. Shall we go with 768KB, or even 1MB?
>>
>> 768K would affect fewer existing partition maps (many of which leave 1M
>> for U-Boot and environment combined), but 1M might be better for new
>> boards.  And of course it would be nice if someone could spare some time
>> to try to slim things down (finer-grained compile-time config,
>> speed/size tradeoffs, etc).
>>
>>> For the first step, I think we don't have to increase size for all
>>> targets. We can adjust those with CONFIG_SYS_TEXT_BASE=0xeff80000. Those
>>> are the most recent used. There are other targets which don't use NOR
>>> flash boot method. They should be considered as well.
>>>
>>> It is per board configuration. But it may be better if we keep them
>>> consistent.
>>
>> I don't think it's worth trying to keep them consistent.  Leave alone
>> old boards that are not pushing the limit, and where testing and user
>> education would be a hassle, and let newer boards where more features
>> are wanted not be constrained by the past.
>>
> 
> I did a quick search for eff80000. Only these boards have it
> 
> include/configs/B4860QDS.h
> include/configs/C29XPCIE.h
> include/configs/corenet_ds.h
> include/configs/HWW1U1A.h
> include/configs/MPC8536DS.h
> include/configs/MPC8572DS.h
> include/configs/P1010RDB.h
> include/configs/P1022DS.h
> include/configs/P1023RDB.h
> include/configs/P1023RDS.h
> include/configs/P1_P2_RDB.h
> include/configs/p1_p2_rdb_pc.h
> include/configs/p1_twr.h
> include/configs/P2020DS.h
> include/configs/P2041RDB.h
> include/configs/T1040QDS.h
> include/configs/t4qds.h
> 

Scott,

Are SPL and TPL boot methods immune from the size issue here?

York

  reply	other threads:[~2013-10-16 17:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 18:29 [U-Boot] powerpc/mpc85xx: Increase image size York Sun
2013-10-11 18:39 ` Scott Wood
2013-10-11 18:56   ` York Sun
2013-10-16 17:41     ` York Sun [this message]
2013-10-16 19:37       ` Scott Wood
2013-10-16 20:22         ` York Sun
2013-10-16 20:29           ` Scott Wood
2013-10-16 20:32             ` York Sun
2013-10-16 20:33               ` Scott Wood
2013-10-16 20:38                 ` York Sun
2013-10-16 20:41                   ` Scott Wood
2013-10-16 20:44                     ` York Sun
2013-10-16 21:23                       ` Scott Wood
2013-10-16 22:43                         ` York Sun
2013-10-17  1:35                           ` Kushwaha Prabhakar-B32579

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=525ECFD4.4080704@freescale.com \
    --to=yorksun@freescale.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