All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: 440GX MMU problem
@ 2004-12-03 21:56 VanBaren, Gerald (AGRE)
  2004-12-04 14:04 ` (Very) Simple question(s) compared to group topics Bora Þahin
  0 siblings, 1 reply; 4+ messages in thread
From: VanBaren, Gerald (AGRE) @ 2004-12-03 21:56 UTC (permalink / raw)
  To: Barbier, Renaud (GE Infrastructure), Matt Porter; +Cc: linuxppc-embedded


> -----Original Message-----
> From: linuxppc-embedded-bounces@ozlabs.org=0D
> [mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of=0D
> Barbier, Renaud (GE Infrastructure)
> Sent: Friday, December 03, 2004 3:53 PM
> To: Matt Porter
> Cc: linuxppc-embedded@ozlabs.org
> Subject: RE: 440GX MMU problem
>=0D
> actually, I just loaded linux at memory offset=0D
> 0x10000000(above 256MB) and in this case it is able to boot=0D
> and use the full 512MB.
> there maybe indeed something broken.
>=0D
> Originally, U-boot did not map the full 512MB but only 256MB.
> I wonder if that could be a possible source of my problem.

Disclaimer: I don't have experience with the 4xx family, but won't stop
me from speculating (which drives Wolfgang crazy when I guess wrong ;-).

On the 82xx u-boot uses BATs to map memory.  On the 82xx, BATs are
limited to 256MBytes per BAT.  I'm guessing you are running into this.
Somewhere in your u-boot it doesn't know how to go beyond the 256MByte
boundary.

On u-boot, check out the use of "CONFIG_VERY_BIG_RAM".  It doesn't look
like it applies directly to your board/processor, but you may be able to
enhance your system using it or a similar concept.

gvb


******************************************
I apologize for the following message brought to you by the Lawyers'
League of IdioSpeak:

******************************************
The information contained in, or attached to, this e-mail, may contain=
 confidential information and is intended solely for the use of the=
 individual or entity to whom they are addressed and may be subject to=
 legal privilege.  If you have received this e-mail in error you should=
 notify the sender immediately by reply e-mail, delete the message from=
 your system and notify your system manager.  Please do not copy it for any=
 purpose, or disclose its contents to any other person.  The views or=
 opinions presented in this e-mail are solely those of the author and do=
 not necessarily represent those of the company.  The recipient should=
 check this e-mail and any attachments for the presence of viruses.  The=
 company accepts no liability for any damage caused, directly or=
 indirectly, by any virus transmitted in this email.
******************************************

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-12-04 16:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-03 21:56 440GX MMU problem VanBaren, Gerald (AGRE)
2004-12-04 14:04 ` (Very) Simple question(s) compared to group topics Bora Þahin
2004-12-04 15:08   ` Mark Chambers
2004-12-04 16:42     ` Jon Masters

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.