public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] cfi_flash.c patches
Date: Fri, 19 Aug 2005 13:36:30 -0500	[thread overview]
Message-ID: <430626AE.9030607@orkun.us> (raw)
In-Reply-To: <00b301c5a476$5c707fe0$212d4cdc@smkim>

Dear Sangmoon,

I've examined your patch for clearing the protection of flash sectors
automatically during flash init. As a matter of fact a similar patch was
also proposed by someone else and I had commented on it as well.

I think this is wrong approach. These sectors are protected for a reason
(to prevent accidental writes - forgetting to enable protection).

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.

CFG_FLASH_PROTECTION will enable the "protect  off" command to disable
protection properly on these sectors as it should.

IMHO, No patch is needed here! Perhaps we need to add a couple of
comment lines in README (DULG?) for documentation purposes. Wolfgang,
can you comment here.

Best regards,
Tolunay

Sangmoon Kim wrote:
> Hi,
> The two patches attached are for drivers/cfi_flash.c.
> 
> cfi_flash-protect.patch adds CFG_FLASH_PROTECT_CLEAR
> because for some flash memories(such as 28F320C3)
> all banks are protected after reset.
> 
> cfi_flash-buffer.patch makes write_buff not to call 
> flash_write_cfibuffer if buffer_size is1.
> Because for flash memories with buffer_size 1,
> buffer write is not supported.
> 
> Regards,
> Sangmoon Kim

  reply	other threads:[~2005-08-19 18:36 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 [this message]
2005-08-22  5:37   ` Sangmoon Kim
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=430626AE.9030607@orkun.us \
    --to=listmember@orkun.us \
    --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