public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] flash hardware protection with CFI driver does not autoprotect monitor completely
Date: Mon, 19 Nov 2007 11:10:37 +0100	[thread overview]
Message-ID: <200711191110.38158.sr@denx.de> (raw)
In-Reply-To: <200711191104.21853.matthias.fuchs@esd-electronics.com>

Hi Matthias,

On Monday 19 November 2007, Matthias Fuchs wrote:
> > Yes, I would prefer size too. This would lead to something like this on
> > 4xx boards:
> >
> > #define CONFIG_FLASH_AUTOPROTECT_LIST { {CFG_MONITOR_BASE,
> > CFG_MONITOR_LEN} }
>
> This looks fine and I will start voting for this, too.

;)

> I am wondering if it is possible to get rid of the current autoprotection
> code (3 x flash_protect for monitor, env and 2nd env) in
> drivers/cfi_flash.c and fully implement it through the AUTOPROTECT_LIST
> without modifyiny all board config files. Any nice idea?

Not really. But it sounds like a good idea.

> Especially on 4xx when you like to have sometinhg like
>
> #define CONFIG_FLASH_AUTOPROTECT_LIST { {CFG_MONITOR_BASE, CFG_MONITOR_LEN}
> }
>
> in your config file you will flash_protect most of the bootloader flash
> space twice.

Yes.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

      reply	other threads:[~2007-11-19 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 18:59 [U-Boot-Users] flash hardware protection with CFI driver does not autoprotect monitor completely Matthias Fuchs
2007-11-18 19:31 ` Wolfgang Denk
2007-11-18 21:14   ` Matthias Fuchs
2007-11-18 21:52     ` Wolfgang Denk
2007-11-19  6:14       ` Stefan Roese
2007-11-19 10:04         ` Matthias Fuchs
2007-11-19 10:10           ` Stefan Roese [this message]

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=200711191110.38158.sr@denx.de \
    --to=sr@denx.de \
    --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