This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
dynamic memory detection
- From: alfred hitch <alfred dot hitch at gmail dot com>
- To: ecos-devel at ecos dot sourceware dot org
- Date: Tue, 10 May 2005 03:36:11 -0400
- Subject: dynamic memory detection
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=lc8WORWeHOoGn54JP2/u9dD7Pl2D7vgEKtKeupJTpRIRZC1gq3o7PXSC178F0XzUTOaVzgCwfGQm1SPKsFpicZiR1b9i+fy1Mvsn7Ly6q2DdHzRSZHVgdUbBcE6ACp6N49n0RU9agSnwKPx3YLcQopoapfavOWWf533b8dCaTkg=
- Reply-to: alfred hitch <alfred dot hitch at gmail dot com>
Hi All,
I am working on a IXDP425 based plattform,
If I understand it correctly there is no bios on it, and so for
physical memory on the system, redboot has to depend on constant /
#defines at compile time.
What if one wants to dynamically detect these ?
Why cannot we read the memory registers, while we are in redboot and
set up things accordingly ??
( I remember doing something similar while playing around in netbsd,
from smbus via open i/o ports it used to read the memory rows,
coloumns etc and find out the size)
I am sure there is some glitch in doing this, and I am missing
something basic here,
can someone please correct me here.
Cheers,
Alfred