public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Saving environment variables in MMC
Date: Wed, 31 Mar 2010 16:34:30 +0200	[thread overview]
Message-ID: <m2aatopnk9.fsf@ohwell.denx.de> (raw)
In-Reply-To: <421570.65265.qm@web50102.mail.re2.yahoo.com> (Nitin Mahajan's message of "Wed, 31 Mar 2010 04:28:01 -0700 (PDT)")

Hi Nitin,

> Thanks for the information. I just wanted to have a feedback, whether
> having a use-case of writing env variables from Linux User space is a
> good idea or is not recommended?

You found tools/env/fw_env.c showing that this functionality is indeed
foreseen and used.

It is rather common to write to the U-Boot environment in projects for
example to switch to a new set of kernel+file system after an update
from within linux for the next boot.

Is this feedback enough?

Cheers
  Detlev

-- 
The structure of a system reflects the structure of the organization
that built it.
                                        -- Richard E. Fairley
--
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

  parent reply	other threads:[~2010-03-31 14:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 15:21 [U-Boot] Saving environment variables in MMC Nitin Mahajan
2010-03-29 17:42 ` Mike Frysinger
2010-03-30 12:04   ` Nitin Mahajan
2010-03-30 12:53     ` Frans Meulenbroeks
2010-03-31 10:47       ` Stefano Babic
2010-03-31 11:28         ` Nitin Mahajan
2010-03-31 13:53           ` Stefano Babic
2010-03-31 14:34           ` Detlev Zundel [this message]
2010-04-01  3:43             ` Nitin Mahajan
2010-04-01 12:05               ` Detlev Zundel
2010-04-01 12:25                 ` Nitin Mahajan
2010-04-02  8:16                 ` Nitin Mahajan

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=m2aatopnk9.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