From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] flash protect question
Date: Thu, 24 Feb 2005 23:35:32 +0100 [thread overview]
Message-ID: <20050224223537.B558AC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 21 Feb 2005 15:07:21 EST." <6.1.1.1.0.20050221150114.01dec810@ptg1.spd.analog.com>
In message <6.1.1.1.0.20050221150114.01dec810@ptg1.spd.analog.com> you wrote:
>
> - is the structure info->protect[n] suppose to be stored in non-volatile
> memory on a "saveenv"? It didn't seem to be, and thus every time I do a
No, it is not.
> 'reset', it current is set to the default (protect U-boot and nothing else.
Wrong. The default is to protect U-Boot and the envrionment variables.
> It didn't really say in the Manual if the software protection was volatile
> or not.
You may call it volatile.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I can't say I've ever been lost, but I was bewildered once for three
days. - Daniel Boone (Attributed)
prev parent reply other threads:[~2005-02-24 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 20:07 [U-Boot-Users] flash protect question Robin Getz
2005-02-23 8:24 ` Shawn Jin
2005-02-24 22:35 ` Wolfgang Denk [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=20050224223537.B558AC1430@atlas.denx.de \
--to=wd@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