From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] hardware flash protect kept during a reboot?
Date: Mon, 17 May 2010 09:11:22 -0500 [thread overview]
Message-ID: <4BF14E8A.3030804@freescale.com> (raw)
In-Reply-To: <201005171055.05858.sr@denx.de>
Stefan Roese wrote:
> This protection is chip specific. IIRC, then some Intel (Strata) chips either
> protect all sectors or have a sectore-wise protection mechanism. You need to
> check your FLASH documentation for the exact behaviour. Which chip are you
> using?
I just want to know whether hardware protection works at all for anyone
through a reboot. Is the CFI "protect sector" command persistent through a
hardware power reset or power loss?
> Please note that we have the special "unlock" env variable. By setting it to
> "yes", all sectors will be unlocked upon startup. At least on Intel Strata
> FLASH chips.
I put a printf() in flash_real_protect(), so I know that's not the problem.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-05-17 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 19:33 [U-Boot] hardware flash protect kept during a reboot? Timur Tabi
2010-05-17 8:55 ` Stefan Roese
2010-05-17 14:11 ` Timur Tabi [this message]
2010-05-18 8:10 ` Stefan Roese
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=4BF14E8A.3030804@freescale.com \
--to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.