From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot common/environment.c
Date: Tue, 19 May 2009 16:34:23 +0200 [thread overview]
Message-ID: <m2pre55fgw.fsf@ohwell.denx.de> (raw)
In-Reply-To: <OF015059E0.9A8612E5-ON652575BB.003C64CF-652575BB.003D26AC@lntemsys.com> (Deepak Gopalakrishnan's message of "Tue, 19 May 2009 16:47:50 +0530")
Hi Deepak,
> im using u-boot-1.1.5_atmel_1.2 and want to add a new environment variable
I doubt that you will get much support with this U-Boot version here on
the list. Use latest code if you want to get help.
> for uboot version...my doubt --is it enough that i add this in the env_t
> environment __PPCENV__ .
This all sounds very fishy - you're working on an ARM platform and you
change something with a tag __PPCENV__? Well, let's see, oh it looks
like you're looking at what is common/env_embedded.c in latest code.
Note that this is only for board configuration which embed the
environment *inside* the text segment, because of unusal requirements of
the flash layout. This is definitely not the norm - does your
configuration use CONFIG_ENV_IS_EMBEDDED?
> Also for each entry in this structure there is a macro defined, so if i
> add version as a new env variable..so this is wat i have made change in
> common/environment.c
> line 179 where env_t environment __PPCENV__ is defined
>
> #ifdef U_BOOT_VERSION
> "u-boot_version=" U_BOOT_VERSION
> #endif
>
> is this enough...?
The environment is a dynamic data section which usually lives outside of
U-Boot code in its own data location. Of course we can change the
environment in a running system, so the compiled in default environment
- or even the embedded environment is only relevant if the "normal"
environment is not accessible, e.g. when flashing a module for the first
time or after a complete erase operation.
Otherwise the "normal" envirnment will be used and even if you change
the compiled in set, you will not see much difference if you don't erase
the environment on an update.
Do you see the conceptual differences here?
Cheers
Detlev
--
Q: Does that mean we also shouldn't be using IRQF_SAMPLE_RANDOM on
interrupt [sources]?
A: Yes. The flag needs to be taken out and shot.
-- Matt Mackall <1239116251.14392.133.camel@calx>
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
prev parent reply other threads:[~2009-05-19 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 18:32 [U-Boot-Users] Add a new command to U-Boot Carlos Filipe Silva
2005-11-15 18:55 ` Cliff Brake
2009-05-07 13:35 ` [U-Boot] " Deepak Gopalakrishnan
2009-05-07 13:40 ` Jerry Van Baren
2009-05-07 13:59 ` Deepak Gopalakrishnan
2009-05-07 15:21 ` Subodh Nijsure
2009-05-08 13:21 ` Deepak Gopalakrishnan
2009-05-08 13:20 ` Jerry Van Baren
2009-05-11 5:32 ` [U-Boot] Uboot reloaction scheme Deepak Gopalakrishnan
2009-05-11 8:16 ` [U-Boot] Add a new command to U-Boot Drasko DRASKOVIC
2009-05-11 14:12 ` [U-Boot] uboot relocate_code() function Deepak Gopalakrishnan
2009-05-11 14:19 ` Liu Dave-R63238
2009-05-11 15:52 ` Timur Tabi
2009-05-11 18:22 ` Scott Wood
2009-05-12 13:47 ` [U-Boot] start.s file Deepak Gopalakrishnan
2009-05-12 14:30 ` Detlev Zundel
2009-05-18 13:18 ` [U-Boot] u-boot version Deepak Gopalakrishnan
2009-05-18 13:16 ` Wolfgang Denk
2009-05-19 9:29 ` Deepak Gopalakrishnan
2009-05-19 14:14 ` Detlev Zundel
2009-05-19 14:41 ` Deepak Gopalakrishnan
2009-05-19 14:40 ` Detlev Zundel
2009-05-20 4:28 ` Deepak Gopalakrishnan
2009-05-19 11:17 ` [U-Boot] U-boot common/environment.c Deepak Gopalakrishnan
2009-05-19 14:34 ` Detlev Zundel [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=m2pre55fgw.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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