From: Angelos Manousarides <amanous@inaccessnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Dynamic location of the environment sector
Date: Mon, 26 Jun 2006 17:57:24 +0300 [thread overview]
Message-ID: <449FF5D4.8050007@inaccessnetworks.com> (raw)
In-Reply-To: <449A78D5.1040607@inaccessnetworks.com>
Angelos Manousarides wrote:
> env_offset is defined at common/environment.c, and this is the defined
> used by other boards as well.
> BUT:
>
> $ arm-linux-objdump -d common/environment.o
>
> common/environment.o: file format elf32-littlearm
>
> Disassembly of section .text:
>
> 00000000 <env_size>:
> 0: 00 80 00 00 ....
>
> 00000004 <environment>:
> 4: 85 6f 43 92 62 6f 6f 74 64 65 6c 61 79 3d 35 00
> .oC.bootdelay=5.
> 14: 62 61 75 64 72 61 74 65 3d 31 31 35 32 30 30 00
> baudrate=115200.
> ...
>
Well, I decided to change the linker script to :
cpu/pxa/start.o (.text)
. = 16 * 1024 - 4;
common/environment.o (.text)
*(.text)
This way the environment will be alligned at the right address and I
don't have to change the u-boot code.
What is the story of the env_size variable? The tools tin tools/env/* do
not use this variable, the environment size is retrieved from the
configuration files.
The only reference I found was in tools/envcrc.c:
#ifdef ENV_IS_EMBEDDED
extern unsigned int env_size;
extern unsigned char environment;
#endif /* ENV_IS_EMBEDDED */
These declarations though are not used anywhere on the code that follows!
In the actual u-boot code (not the tools) there is no usage. Is it some
kind of a legacy mechanism, leftover from older versions of u-boot?
--
Angelos Manousaridis
next prev parent reply other threads:[~2006-06-26 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:55 [U-Boot-Users] Dynamic location of the environment sector Angelos Manousarides
2006-06-14 14:31 ` Wolfgang Denk
2006-06-21 10:48 ` Angelos Manousarides
2006-06-21 14:11 ` Wolfgang Denk
2006-06-21 17:16 ` Angelos Manousarides
2006-06-21 17:21 ` Angelos Manousarides
2006-06-21 20:47 ` Wolfgang Denk
2006-06-21 20:46 ` Wolfgang Denk
2006-06-22 10:21 ` Angelos Manousarides
2006-06-22 10:44 ` Wolfgang Denk
2006-06-22 11:02 ` Angelos Manousarides
2006-06-26 14:57 ` Angelos Manousarides [this message]
2006-06-26 21:10 ` Wolfgang Denk
2006-06-27 9:20 ` Angelos Manousarides
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=449FF5D4.8050007@inaccessnetworks.com \
--to=amanous@inaccessnetworks.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 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.