All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpc83xx: increase BOOTMAPSZ to 16MB
Date: Thu, 13 Nov 2008 01:51:57 +0300	[thread overview]
Message-ID: <20081112225157.GA29433@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20081112155713.d410ccdd.kim.phillips@freescale.com>

On Wed, Nov 12, 2008 at 03:57:13PM -0600, Kim Phillips wrote:
> On Thu, 6 Nov 2008 16:31:26 +0300
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
> 
> > As space expands, so does the software. Today the kernel with built-in
> > initramfs image is likely to not fit into 8MB limit. It feels safe to
> > increase BOOTMAPSZ to 16MB, since the Linux actually maps 16MB on 6xx
> > PPCs (two BATs, 8MB each).
> > 
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> > ---
> > 
> > p.s. The patch for the whole tree is quite big, so let's start
> > with 83xx.
> 
> ack,

Great, thanks.

> I'm ok with this operation starting in 83xx land, but it may be
> worth investigating whether it can be made a one-shot directly with WD,
> just as the CFG_ -> CONFIG_SYS_ switch just happened.  dunno. If we
> don't hear from WD soon, I'll put this in mpc83xx's next branch.

Please don't queue this patch yet. I'll send an updated version
soon, that will also define CFG_BOOTM_LEN (so that bootm command
will able to gunzip 16MB images).

> > pp.s. Maybe we could fector out these defines into
> > include/configs/ppc6xx-common.h?
> 
> sure, but maybe that can wait until the base domain granularity becomes
> more accurately visible...

Ok, makes sense.

-- 
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2

      reply	other threads:[~2008-11-12 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 13:31 [U-Boot] [PATCH] mpc83xx: increase BOOTMAPSZ to 16MB Anton Vorontsov
2008-11-12 21:57 ` Kim Phillips
2008-11-12 22:51   ` Anton Vorontsov [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=20081112225157.GA29433@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.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.