linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] POWERPC 8xx: bump up initial memory limit for 8xx
Date: Wed, 01 Aug 2007 14:13:24 -0500	[thread overview]
Message-ID: <46B0DB54.8090705@freescale.com> (raw)
In-Reply-To: <20070717011723.23549.44672.stgit@localhost.localdomain>

Vitaly Bordug wrote:
> From: John Traill <john.traill@freescale.com>
> 
> The 8xx can only support a max of 8M during early boot ( it seems a lot of
> 8xx boards only have 8M so the bug was never triggered ). The following
> change makes it able to run with 128M.
> 
> Signed-off-by: Vitaly Bordug <vitb@kernel.crashing.org>
> 
> ---
> 
>  arch/powerpc/mm/init_32.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/powerpc/mm/init_32.c b/arch/powerpc/mm/init_32.c
> index e1f5ded..7cee86d 100644
> --- a/arch/powerpc/mm/init_32.c
> +++ b/arch/powerpc/mm/init_32.c
> @@ -133,6 +133,9 @@ void __init MMU_init(void)
>  	/* 601 can only access 16MB at the moment */
>  	if (PVR_VER(mfspr(SPRN_PVR)) == 1)
>  		__initial_memory_limit = 0x01000000;
> +	/* 852 can only access 8MB at the moment */
> +	if (PVR_VER(mfspr(SPRN_PVR)) == 0x50)
> +		__initial_memory_limit = 0x00800000;

The comment should refer to 8xx, not 852, as this is a property of code 
in head_8xx.S and not the chip itself.

Otherwise,
Acked-by: Scott Wood <scottwood@freescale.com>

-Scott

      reply	other threads:[~2007-08-01 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  1:17 [PATCH] POWERPC 8xx: bump up initial memory limit for 8xx Vitaly Bordug
2007-08-01 19:13 ` Scott Wood [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=46B0DB54.8090705@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=vitb@kernel.crashing.org \
    /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;
as well as URLs for NNTP newsgroup(s).