public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Why is ENV_IS_EMBEDDED globally define when NAND bootloader is built ?
Date: Mon, 20 Nov 2006 10:21:03 +0100 (MET)	[thread overview]
Message-ID: <200611201022.13649.sr@denx.de> (raw)
In-Reply-To: <9E50B2A5FE44294CBF877745D9A4125FC1FA6E@az33exm24.fsl.freescale.net>

Hi Nick,

On Monday 20 November 2006 09:16, Spence Nick-rxtd10 wrote:
> I am trying to set up a NAND_SPL bootloader for a different PowerPC
> processor.

Good. Additional board/cpu support for this new U-Boot NAND booting feature is 
very welcome. :-)

> I want to store the environment variables in the NAND Flash at a
> location above the boot loader, so that I can reprogram the bootloader
> without overwriting the variables when I copy the u-boot-nand.bin image
> into the NAND flash.

Understood. Just a side note: You could use a command that runs "saveenv" upon 
updating the U-Boot image. This way you won't loose the environment.

> However in the changes made on Sept 12, the include/environment.h file
> was modified to define ENV_IS_EMBEDDED whenever CONFIG_NAND_U_BOOT is
> defined.
>
> Is there any reason that this configuration setting cannot be moved into
> the board specific include file instead ?

Not really. We can move this define into some board specific place. We should 
use the define "CFG_ENV_IS_EMBEDDED" in the board config file though and not 
the define "ENV_IS_EMBEDDED".

Best regards,
Stefan

      reply	other threads:[~2006-11-20  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  8:16 [U-Boot-Users] Why is ENV_IS_EMBEDDED globally define when NAND bootloader is built ? Spence Nick-rxtd10
2006-11-20  9:21 ` Stefan Roese [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=200611201022.13649.sr@denx.de \
    --to=sr@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