From: llandre <r&d2@dave-tech.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Support for SRAM in u-boot
Date: Tue, 22 Jan 2008 17:32:47 +0100 [thread overview]
Message-ID: <47961AAF.7000006@dave-tech.it> (raw)
In-Reply-To: <115A3AE4BC001B47BDE607FDE8DBEB3004A14E01@OXCH30IV.int.olivetti.corp>
> I know that u-boot provides commands to access memory but I have seen that in some cases it also properly set-up board specific HW resources included flash, SDRAM etc (I think but not really sure because i'm a newbe on this subject, that some of these initialization could be provided by updating the u-boot with the proper patches).
> Our problem is that neither the fist atmel bootstrap code (AT91Bootstrap) nor the atmel (AT91SAM9261 board) u-boot patch provide initialization for that kind of SRAM.
This is the job you have to do to port U-Boot to your platform.
In platform-specific initialization code (typically located in
board/<your_board>/<your_board>.c) you can add this stuff.
Regards,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave.eu
email: r&d2 at dave-tech.it
prev parent reply other threads:[~2008-01-22 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:02 [U-Boot-Users] Support for SRAM in u-boot Cacre
2008-01-22 14:09 ` llandre
2008-01-22 15:25 ` Cacre
2008-01-22 16:32 ` llandre [this message]
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=47961AAF.7000006@dave-tech.it \
--to=r&d2@dave-tech.it \
--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