* Re: sandpoint woes.
[not found] <Pine.GSO.4.21.0010261820540.18282-100000@stekt6>
@ 2000-10-26 17:16 ` Mark A. Greer
0 siblings, 0 replies; only message in thread
From: Mark A. Greer @ 2000-10-26 17:16 UTC (permalink / raw)
To: Topi Kanerva, linuxppc-embedded
Topi Kanerva wrote:
> init started: BusyBox v0.43 (2000.07.20-00:29+0000) multi-call binary
> Sorry, your computer does not have enough memory. \
>
> ...
> DINK reports that my sandpoint does have 64M of memory, but when Linux
> kernel boots, it only finds 32M of memory (29056k available (944k kernel
> code, 404k data, 172k init)) ... I even tried to put a "mem=64M" kernel
> bootoption, but it didn't make any difference. Any ideas?
Yes, DINK lies. At least on all the boards I have, there are 32 MB of memory
even though DINK says there are 64MB (DINK enables an extra memory bank of 32 MB
in the mem ctlr even though the memory doesn't exist). To combat that, I
hard-coded 32MB--yes, an ugly hack--in
arch/ppc/mm/init.c:sandpoint_find_end_of_memory(). If you believe you really
have 64 MB, go ahead and change that routine to report 64MB or whatever you
think is appropriate.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-10-26 17:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.GSO.4.21.0010261820540.18282-100000@stekt6>
2000-10-26 17:16 ` sandpoint woes Mark A. Greer
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).