From: Robin Gilks <robin.gilks@tait.co.nz>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Function pointers after relocation
Date: Tue, 15 Jul 2003 12:21:44 +1200 [thread overview]
Message-ID: <3F134918.5020908@tait.co.nz> (raw)
In-Reply-To: <20030714111438.78C9EC6D82@atlas.denx.de>
Hi Wolfgang
Wolfgang Denk wrote:
> Dear Robin,
>
> in message <3F03564A.4090807@tait.co.nz> you wrote:
>
>>>Which part of the code are you speaking of?
>>
>>Opps - a typo in the example!! I meant to say the pointer env_get_char()
>>which is initialised to env_get_char_init and remains pointing at the
>>Flash copy of that function after relocation.
>
>
> I cannot verify this problem. It works fine for me (i. e.
> env_get_char() will be relocated correctly to point to the in-RAM
> copy of the function).
>
Yup - you're quite right :-))
This was a symptom of our incorrect config where CONFIG_MONITOR_LEN was
incorrectly defined making the code think the environment was embedded
when it wasn't. Our debugging logic was suffering a Friday afternoon (or
maybe it was a blond) moment...
I hope to release the MPC866ADS board updates to you this week - just
cleaning up the diffs against the latest CVS now.
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks at tait.co.nz
New Zealand
prev parent reply other threads:[~2003-07-15 0:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 5:04 [U-Boot-Users] Function pointers after relocation Robin Gilks
2003-07-02 14:31 ` Wolfgang Denk
2003-07-02 22:01 ` Robin Gilks
2003-07-02 22:35 ` Nye Liu
2003-07-08 5:48 ` Robin Gilks
2003-07-09 4:46 ` Robin Gilks
2003-07-09 16:15 ` nyet at mrv.com
2003-07-09 16:37 ` Wolfgang Denk
2003-08-02 0:18 ` Nye Liu
2003-08-02 9:37 ` Wolfgang Denk
2003-08-03 8:24 ` nyet at mrv.com
2003-08-03 11:11 ` Wolfgang Denk
2003-08-03 21:35 ` Robin Gilks
2003-07-14 11:14 ` Wolfgang Denk
2003-07-15 0:21 ` Robin Gilks [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=3F134918.5020908@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--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