All of lore.kernel.org
 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 15:43:54 -0700	[thread overview]
Message-ID: <525F16AA.90609@freescale.com> (raw)
In-Reply-To: <1381958598.7979.749.camel@snotra.buserror.net>

On 10/16/2013 02:23 PM, Scott Wood wrote:
> On Wed, 2013-10-16 at 13:44 -0700, York Sun wrote:
>> On 10/16/2013 01:41 PM, Scott Wood wrote:
>>> On Wed, 2013-10-16 at 13:38 -0700, York Sun wrote:
>>>> On 10/16/2013 01:33 PM, Scott Wood wrote:
>>>>> On Wed, 2013-10-16 at 13:32 -0700, York Sun wrote:
>>>>>> On 10/16/2013 01:29 PM, Scott Wood wrote:
>>>>>>> On Wed, 2013-10-16 at 13:22 -0700, York Sun wrote:
>>>>>>>> On 10/16/2013 12:37 PM, Scott Wood wrote:
>>>>>>>>> On Wed, 2013-10-16 at 10:41 -0700, York Sun wrote:
>>>>>>>>>> Are SPL and TPL boot methods immune from the size issue here?
>>>>>>>>>
>>>>>>>>> Sort of.  We still need to fit inside existing partition tables.
>>>>>>>>>
>>>>>>>>
>>>>>>>> PBL boot will be broken if the image size is bigger than 512KB, right?
>>>>>>>
>>>>>>> It has to be even smaller than that, to make room for early data.
>>>>>>>
>>>>>>
>>>>>> So if we go with 768KB, do we have to convert all PBL boot to SPL boot?
>>>>>
>>>>> Only the targets that need the extra space.
>>>>>
>>>>
>>>> We have T4, B4 and corenet_ds using PBL boot. They most likely will
>>>> exceed the 512KB soon, if not yet. It maybe easier to change all of them
>>>> togther, than one by one.
>>>
>>> There's no reason to change them all at once.  It doesn't make anything
>>> easier; it just means you have to do a bunch of testing all at once, and
>>> force a change in procedure for users on boards where it otherwise would
>>> not have been required.
>>
>> You are right here.
>>
>>>
>>> Plus, the 512K limit is for e500v2-based chips.  Newer chips have CPC
>>> for SRAM which is larger than 512K.
>>>
>>
>> Hmm? T4240 has 512KB CPC.
> 
> Each CPC is 512K, but there are three of them.  Is it possible to use
> more than one for SRAM, contiguously?

I think it is possible to use two CPC. The PBL boot method is hard-coded
to take 512KB u-boot.bin and generate u-boot.pbl. It surely can be
improved. My point is making a move for all concerned platforms may be
easier for maintenance.

York

  reply	other threads:[~2013-10-16 22:43 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
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 [this message]
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=525F16AA.90609@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.