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: Mon, 22 Aug 2005 12:02:48 -0500	[thread overview]
Message-ID: <430A0538.2040908@orkun.us> (raw)
In-Reply-To: <20050822075807.4D5D0352B0C@atlas.denx.de>

Wolfgang Denk wrote:

>In message <4309712D.1040301@orkun.us> you wrote:
>  
>
>>Convenience is irrelevant. This flash is obviously designed with data
>>protection as priority.
>>    
>>
>
>Convenience is not irrelevant. The existence of U-Boot itself is just
>for convenience,
>  
>
I think "protect off" command is the convenience enough for this situation.

>We don't care what the people who designed the flash had in mind.  In
>U-Boot, the design is as follows:
>
>* All flash is writable by default.
>  
>
Why do you even attempt to provide software protection  for some sectors 
of flash when the chip does not provide such protection then?

>* Some parts of the flash may be  either  implictely  or  explicitely
>  protected.
>
>* Implicit protection: this covers those areas of the flash that  are
>  used  to  store  data  that  are  required for correct operation of
>  U-Boot and the hardware, i. e.
>
>  - the U-Boot code and data
>  - environment variables
>  - any FPGA images etc. which are necessary for correct HW operation
>  
>

Why do you override the policy of other applications for sectors that 
U-Boot has no actual use itself. Why do you unlock them all and present 
the opportunity of loss of critical data for other parts of the software 
solution? I would argue that there may be important and critical data 
stored in those sectors that are "required for correct operation of 
software" that runs on the CPU after U-Boot is done. Why do you think 
these parts deserve lesser protection?

Best regards,
Tolunay

  reply	other threads:[~2005-08-22 17:02 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
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 [this message]
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=430A0538.2040908@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