From: David Updegraff <dave@cray.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] i386 ram data segment
Date: Thu, 29 Jan 2004 14:14:05 -0600 [thread overview]
Message-ID: <4019698D.5090908@cray.com> (raw)
Hi.
May I request help in understanding the i386boot_romdata_* values? I am a
newbie to the PC-compat. world; starting work on an SC520 board, working from
helpfull guidance in sc5230_cdp.
Is there a sub-group of uboot-i386 I should direct this to?
Is the value of 0x400000 (4M) critical there? Or why so?
Then when making u-boot.bin with objcopy, if I include --gap-fill, I
end up logically with an absolutely HUGE .bin; so presumeably one has
to patch that.
Cheers.
--
Dave Updegraff <dave@cray.com>
reply other threads:[~2004-01-29 20:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4019698D.5090908@cray.com \
--to=dave@cray.com \
--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