From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] porting u-boot
Date: Tue, 30 Nov 2004 12:44:33 +0100 [thread overview]
Message-ID: <41AC5D21.8040107@web.de> (raw)
I'm still into porting u-boot to a full-custom board.
The u-boot README says that the u-boot will scan for my SDRAM and find
out how much I have.
I suppose that will only work if I write a custom SDRAM-setup-procedure
..../u-boot/board/CUSTOMBOARD/customboard.c ? Is that right?
If so, is there any documentation about what needs to be done there?
I believe that the sdram_table array used in all those board_name.c
files contains hexadecimal encoded instructions programming the UPM.. am
I right?
Well... any hints (like, for example, "RTFM manual/ressource name") are
welcome.
Peter Asemann
next reply other threads:[~2004-11-30 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 11:44 Peter Asemann [this message]
2004-11-30 11:57 ` [U-Boot-Users] porting u-boot Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 9:36 [U-Boot-Users] Porting U-boot calvin
2004-09-27 12:08 [U-Boot-Users] porting u-boot 吴兵
2004-09-27 20:22 ` 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=41AC5D21.8040107@web.de \
--to=peter.asemann@web.de \
--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