From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Update OMAP242x for git head (plus sign).
Date: Thu, 29 Sep 2005 17:07:11 -0500 [thread overview]
Message-ID: <433C658F.8010209@orkun.us> (raw)
In-Reply-To: <20050929211701.604B6353AB4@atlas.denx.de>
Wolfgang Denk wrote:
>>Unlocking all sectors on these parts would change the current behavior
>>of the boards unless either the environment variable is defined or board
>>config file is also updated.
>
>
> Yes. From my point of view this means fixing these boards :-)
OK
>>Also, Instead of all black or white, why don't we have unlock regions
>>for partial unlocking sections of flash like like jffs2 partitions? E.g.
>
>
> That would be even more confusing for most users.
>
> Sorry, I can perfectly understand your intentions from a developers
> point of view. But guess how many users there are for each of us
> developers? They outnumber us many, many times. And even if there was
> perfect documentation for each of the ports - guess how many users
> would not read it? Providing the same look and feel across all
> implementations is an important issue for me. And I see it as a part
> of my task as a maintainer to keep the design simple and predictable.
>
> KISS.
OK. Probably an on/off knob for user is enough. I think board designer
needs a bit more help in setting a policy for his/her board.
Would you consider something like CFG_FLASH_PROTECT_LIST in board config
file which defines an array of blocks that needs to be kept protected?
This would be a list similar to CFG_FLASH_BANKS_LIST. This would take
care of important sections of flash (beyond u-boot and environment) that
needs to be protected for that particular board.
Best regards,
Tolunay
next prev parent reply other threads:[~2005-09-29 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 0:01 [U-Boot-Users] [PATCH] Update OMAP242x for git head (plus sign) Woodruff, Richard
2005-09-29 13:24 ` Wolfgang Denk
2005-09-29 20:28 ` Tolunay Orkun
2005-09-29 21:17 ` Wolfgang Denk
2005-09-29 22:07 ` Tolunay Orkun [this message]
2005-09-29 22:20 ` Wolfgang Denk
2005-09-29 23:36 ` Tolunay Orkun
2005-09-30 8:12 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 21:20 Woodruff, Richard
2005-09-28 23:46 ` Wolfgang Denk
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=433C658F.8010209@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