public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] flash hardware protection with CFI driver does not autoprotect monitor completely
Date: Sun, 18 Nov 2007 22:52:00 +0100	[thread overview]
Message-ID: <20071118215200.67EAA243A9@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sun, 18 Nov 2007 22:14:05 +0100." <200711182214.06137.matthias.fuchs@esd-electronics.com>

Dear Matthias,

in message <200711182214.06137.matthias.fuchs@esd-electronics.com> you wrote:
> 
> > I think as a short term fix we might define an additional  area  that
> > needs  to  be  protected  (the reset vector). Mid/long term we should
> > change the code so you  can  pass  a  list  of  areas  (start/end  or
> > start/length  pairs) that will be protected. This would, for example,
> > also allow to keep certain other  areas  (FDT,  kernel  image,  etc.)
> > auto-protected as well - configurable by the user ona per-board base.
> 
> Sometinhg like this?
> 
> Add this to board's config file:
> #define CONFIG_FLASH_AUTOPROTECT_LIST {{0xfffe0000, 0xffffffff}, {0xfe000000, 0xfe0fffff}}

Yes, that's what I meant, although I have to admit that my personal
preference would be to use { start, size }  instead. 

What do you (and others) think?

> And handle this list from the cfi driver:
> 
> diff --git a/drivers/cfi_flash.c b/drivers/cfi_flash.c
> index 5579a1e..0777349 100644
> --- a/drivers/cfi_flash.c
> +++ b/drivers/cfi_flash.c
> @@ -333,11 +333,17 @@ ulong flash_read_long (flash_info_t * info, flash_sect_t sect, uint offset)
> 
>  /*-----------------------------------------------------------------------
>   */
> +struct apl_s {ulong start; ulong end;};
> +
>  unsigned long flash_init (void)
>  {
>         unsigned long size = 0;
>         int i;
> 
> +#if defined(CONFIG_FLASH_AUTOPROTECT_LIST)
> +       struct apl_s apl[] = CONFIG_FLASH_AUTOPROTECT_LIST;
> +#endif
> +
>  #ifdef CFG_FLASH_PROTECTION
>         char *s = getenv("unlock");
>  #endif
> @@ -419,6 +425,16 @@ unsigned long flash_init (void)
>                        CFG_ENV_ADDR_REDUND + CFG_ENV_SIZE_REDUND - 1,
>                        flash_get_info(CFG_ENV_ADDR_REDUND));
>  #endif
> +
> +#if defined(CONFIG_FLASH_AUTOPROTECT_LIST)
> +       for (i = 0; i < sizeof(apl)/sizeof(struct apl_s); i++) {
> +               printf("autoprotecting from %08x to %08x\n", apl[i].start, apl[i].end);
> +               flash_protect (FLAG_PROTECT_SET,
> +                              apl[i].start,
> +                              apl[i].end,
> +                              flash_get_info(apl[i].start));
> +       }
> +#endif
>         return (size);
>  }

Right. That's what I had in mind. Except that I recommend to
s/printf/debug/ ...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Doubt isn't the opposite of faith; it is an element of faith.
- Paul Tillich, German theologian and historian

  reply	other threads:[~2007-11-18 21:52 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 [this message]
2007-11-19  6:14       ` Stefan Roese
2007-11-19 10:04         ` Matthias Fuchs
2007-11-19 10:10           ` Stefan Roese

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=20071118215200.67EAA243A9@gemini.denx.de \
    --to=wd@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