From: Sangmoon Kim <dogoil@etinsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] cfi_flash.c patches
Date: Mon, 22 Aug 2005 14:37:03 +0900 [thread overview]
Message-ID: <002c01c5a6db$8a115ed0$212d4cdc@smkim> (raw)
In-Reply-To: 430626AE.9030607@orkun.us
Dear Tolunay Orkun,
Sorry for late reply.
> I think this is wrong approach. These sectors are protected for a reason
>
But some chips(like 28F320C3 from intel) automatically
protect all sectors after reset.
Although the chips have good reasons to do it.
I think, some boards also have good reasons to undo it.
> You should enable CFG_FLASH_PROTECTION in your board config file. If you
> don't do this U-Boot will do software protection of sectors (which is
> really for those flash chips with no hardware protection capability) and
> "protect off" will not issue unlock commands as you may have witnessed.
>
That's right. Power-on-protected-automatically chips need both
CFG_FLASH_PROTECTION and CFG_FLASH_PROTECT_CLEAR flags.
> CFG_FLASH_PROTECTION will enable the "protect off" command to disable
> protection properly on these sectors as it should.
>
I don't think it is convenient to protect off sectors manually
which is automatically protected during power on.
Best regards,
Sangmoon Kim
next prev parent reply other threads:[~2005-08-22 5:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 4:27 [U-Boot-Users] [PATCH] cfi_flash.c patches Sangmoon Kim
2005-08-19 18:36 ` Tolunay Orkun
2005-08-22 5:37 ` Sangmoon Kim [this message]
2005-08-22 6:31 ` Tolunay Orkun
2005-08-22 7:13 ` Sangmoon Kim
2005-08-22 15:37 ` Tolunay Orkun
2005-08-22 16:17 ` Wolfgang Denk
2005-08-22 16:49 ` Tolunay Orkun
2005-08-22 20:49 ` Wolfgang Denk
2005-08-22 16:41 ` Scott McNutt
2005-08-23 1:53 ` Sangmoon Kim
2005-08-22 7:58 ` Wolfgang Denk
2005-08-22 17:02 ` Tolunay Orkun
2005-08-22 20:53 ` Wolfgang Denk
2005-08-22 22:05 ` Tolunay Orkun
2005-08-22 22:46 ` Wolfgang Denk
2005-08-23 7:14 ` Yuli Barcohen
2005-08-23 8:39 ` Sangmoon Kim
2005-08-23 14:47 ` Brian Waite
2005-08-23 20:24 ` Wolfgang Denk
2005-08-24 5:58 ` Yuli Barcohen
2005-08-24 16:00 ` Detlev Zundel
2005-08-24 21:52 ` Tolunay Orkun
2005-08-24 23:12 ` Wolfgang Denk
2005-08-25 14:37 ` Brian Waite
2005-08-25 16:37 ` Tolunay Orkun
2005-08-26 14:12 ` U-Boot policy on flash protection (was [U-Boot-Users] [PATCH] cfi_flash.c patches) Detlev Zundel
2005-08-26 14:45 ` Wolfgang Denk
2006-02-28 16:34 ` [U-Boot-Users] [PATCH] cfi_flash.c patches Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 18:47 Woodruff, Richard
2005-08-19 20:16 ` Tolunay Orkun
2005-08-19 20:22 Woodruff, Richard
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='002c01c5a6db$8a115ed0$212d4cdc@smkim' \
--to=dogoil@etinsys.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.