public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for setting environment variable from RAM.
Date: Tue, 03 Feb 2009 14:48:48 -0700	[thread overview]
Message-ID: <4988BBC0.4070004@boundarydevices.com> (raw)
In-Reply-To: <20090203201621.C45C38322908@gemini.denx.de>

Wolfgang Denk wrote:
> Dear Eric,
> 
> In message <4988936E.3070504@boundarydevices.com> you wrote:
>>> In the email thread you mentioned above, Detlev mentions 2 alternatives
>>> to the "ramenv" command - loading a uImage script and running it via
>>> autoscr, or modifying autoscr to be able to raw files (non-uImages).
>>> Both of these methods seem cleaner and more flexible at a glance.  Is
>>> there a specific reason using autoscr wouldn't work for your setup?
>>>
>> The customer requesting this feature operates in a regulated environment with
>> pretty strict rules about separation of code and data. Autoscr is kind of
>> a big stick for what we're trying to achieve: (configuring an LCD with
>> settings from a file on SD card).
> 
> Why is it a big stick? It has a couple of significant advantages over
> your implementation:
> 
No offense intended ;) Perhaps I should have said it was a much more powerful feature.

> * It already exissts in mainline.
> * It can set several environment variables at once (and also perform
>   any other commands you might need on your system).
> * It is based on text files which are easy to edit without need for
>   new tools.
> * It will verify that your file has been transmitted correctly.
> 
Don't get me wrong, I'm a big fan of autoscr.

As I mentioned, the customer requesting the feature has a regulatory
requirement any time __code__ changes. They have interpreted boot loader
scripts as being executable, so they have to write checks if the script
changes, but not if "data" changes. They interpret a file containing a
variable as data.

Of course they'll need a code release to get there, ...

>> Our particular need is just for a single environment variable, so the
>> update works pretty well. I started by updating our 'lcdpanel' U-Boot
>> command to read from file, but this is much more useful.
> 
> I suggest you use autoscr instead.
> 
> I think I will reject your patch.
> 
That's reasonable. I don't mind carrying the patch around for this customer,
and you're the one preventing U-Boot from becoming bloated over time.

I appreciate all of your efforts.

Regards,


Eric

  reply	other threads:[~2009-02-03 21:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 15:28 [U-Boot] [PATCH] Add support for setting environment variable from RAM Eric Nelson
2009-02-03 16:00 ` Peter Tyser
2009-02-03 18:56   ` Eric Nelson
2009-02-03 20:16     ` Wolfgang Denk
2009-02-03 21:48       ` Eric Nelson [this message]
2009-02-03 22:08         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2009-02-03  3:28 Eric Nelson
2009-02-05 19:30 ` Wolfgang Denk
2009-02-05 21:15   ` Eric Nelson
2009-02-05 21:26     ` Wolfgang Denk
2009-02-05 21:34       ` Eric Nelson

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=4988BBC0.4070004@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox