From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Reg. CFI flash_init and hardware write protected devices
Date: Wed, 1 Jun 2011 17:34:29 +0200 [thread overview]
Message-ID: <201106011734.29911.sr@denx.de> (raw)
In-Reply-To: <BANLkTi=4+Jh47VRQ=MwZS607foxhrv5OJQ@mail.gmail.com>
Hi Frank,
On Wednesday 01 June 2011 16:33:14 Frank Svendsb?e wrote:
> >> Simply because disabling write-protection is not impossible after
> >> installation. Our device will be located 3000m below sea level.
> >
> > I see.
>
> Hmm.. then you read my mind :) I meant to say "is not possible" and not "is
> not impossible" :)
Yep. I read so fast, that I didn't catch the misspelled words. ;)
> Thanks, this worked for me. Is it ok for you too?
>
> diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
> index 6039e1f..99360af 100644
> --- a/drivers/mtd/cfi_flash.c
> +++ b/drivers/mtd/cfi_flash.c
> @@ -176,6 +176,7 @@ u64 flash_read64(void *addr)__attribute__((weak,
> alias("__flash_read64")));
> #define flash_read64 __flash_read64
> #endif
>
> +
Don't add this empty line.
> /*-----------------------------------------------------------------------
> */
> #if defined(CONFIG_ENV_IS_IN_FLASH) ||
> defined(CONFIG_ENV_ADDR_REDUND) || (CONFIG_SYS_MONITOR_BASE >=
> CONFIG_SYS_FLASH_BASE)
> @@ -2151,7 +2152,8 @@ void flash_protect_default(void)
> #endif
> }
>
> -unsigned long flash_init (void)
> +unsigned long flash_init(void) __attribute__((weak,
> alias("__flash_init"))); +unsigned long __flash_init (void)
> {
> unsigned long size = 0;
> int i;
Looks good. I have no objections. Please go ahead and send this as a "proper"
patch.
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
next prev parent reply other threads:[~2011-06-01 15:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 8:35 [U-Boot] Reg. CFI flash_init and hardware write protected devices Frank Svendsbøe
2011-05-31 12:49 ` Mike Frysinger
2011-05-31 13:25 ` Frank Svendsbøe
2011-05-31 14:01 ` Mike Frysinger
2011-05-31 13:10 ` Stefan Roese
2011-05-31 13:55 ` Frank Svendsbøe
2011-05-31 14:37 ` Stefan Roese
2011-06-01 14:33 ` Frank Svendsbøe
2011-06-01 15:34 ` Stefan Roese [this message]
2011-06-01 16:59 ` Frank Svendsbøe
2011-06-23 13:50 ` Frank Svendsbøe
2011-06-23 15:21 ` Wolfgang Denk
2011-06-23 16:15 ` Frank Svendsbøe
2011-06-23 17:55 ` Wolfgang Denk
2011-06-23 19:05 ` Frank Svendsbøe
2011-06-24 13:59 ` Frank Svendsbøe
2011-06-24 14:26 ` Wolfgang Denk
2011-06-24 19:58 ` Frank Svendsbøe
2011-06-24 20:26 ` Wolfgang Denk
2011-06-24 21:12 ` Frank Svendsbøe
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=201106011734.29911.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.