From: Matej Kupljen <matej.kupljen@ultra.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] memory probe
Date: Wed, 11 May 2005 20:31:41 +0200 [thread overview]
Message-ID: <1115836301.25819.7.camel@orionlinux.starfleet.com> (raw)
In-Reply-To: <aa56107905050919099b9b06b@mail.gmail.com>
Hi
> what if we want same image to work on 2 different memory configuration
> hardware ?
We had such board. One with 32MB and other with 64MB of SDRAM.
We used DIP switches, which were read early in a U-Boot, in
memsetup.S. On the position of this DIP switch we then decided
which path in the mesetup.S to take.
Then, in out dram_init function for our board, we again read the
DIP switch and decide what to report as DRAM size.
BR,
Matej
next prev parent reply other threads:[~2005-05-11 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 2:09 [U-Boot-Users] memory probe Sumit Chauhan
2005-05-11 18:31 ` Matej Kupljen [this message]
2005-05-11 20:56 ` Wolfgang Denk
2005-05-12 8:15 ` Matej Kupljen
2005-05-12 8:42 ` Wolfgang Denk
2005-05-12 9:06 ` Matej Kupljen
2005-05-12 9:43 ` Wolfgang Denk
2005-05-11 18:38 ` Jon Loeliger
2005-05-11 18:44 ` Wolfgang Denk
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=1115836301.25819.7.camel@orionlinux.starfleet.com \
--to=matej.kupljen@ultra.si \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox