From: Gerrit Van de Velde <gvd@denayer.wenk.be>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot and S3c2410
Date: 23 Feb 2004 16:56:02 +0100 [thread overview]
Message-ID: <1077551762.4835.50.camel@nios> (raw)
In-Reply-To: <200402231526.i1NFQrdg032283@mail.wenk.be>
I'm far from an expert on the matter ;)
But I would try to set the addresses to 0x30000000 then. The kernel will
be expanded to RAM first and then a jump will be made to the address in
the RAM to start executing the kernel.
In my situation, I used 0x0 as start/entry. RAM starts on that address
too.
Regards,
Gerrit
On Mon, 2004-02-23 at 16:20, asnua at eircom.net wrote:
> So what is the difference between the load and entry addresses? All of the examples I've seen have the load and entry addresses set to be the same...ish. 0x00000000 & 0x0000000c for PPC
> In my case my SDRAM starts at 0x30000000 and ends at 0x33FFFFFF. My Flash and hence U-Boot is at 0x00.
>
> Does the load and entry address vary depending on whether you are using vmlinux/vmlinux compressed/zImage?
>
> Thanks,
> Dave
next parent reply other threads:[~2004-02-23 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200402231526.i1NFQrdg032283@mail.wenk.be>
2004-02-23 15:56 ` Gerrit Van de Velde [this message]
2004-02-23 16:13 ` [U-Boot-Users] U-Boot and S3c2410 Wolfgang Denk
2004-02-24 18:44 asnua at eircom.net
[not found] <20040223152655.1C51E42F39@denx.de>
2004-02-23 16:05 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 15:20 asnua at eircom.net
[not found] <200402201751.LAA10408@mail.invocon.com>
2004-02-20 18:11 ` Matt Matoushek
2004-02-20 17:46 asnua at eircom.net
[not found] <200402201514.JAA07750@mail.invocon.com>
2004-02-20 16:39 ` Matt Matoushek
[not found] <200402201513.i1KFDEdg026804@mail.wenk.be>
2004-02-20 15:22 ` Gerrit Van de Velde
2004-02-20 18:43 ` Wolfgang Denk
2004-02-20 15:10 asnua at eircom.net
[not found] <200402191119.i1JBJcdg018878@mail.wenk.be>
2004-02-19 11:28 ` Gerrit Van de Velde
2004-02-19 11:16 asnua at eircom.net
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=1077551762.4835.50.camel@nios \
--to=gvd@denayer.wenk.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.