public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: DrEagle <dreagle@doukki.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/5] Fix env address for Sheevaplug board
Date: Wed, 26 Sep 2012 07:35:56 +0200	[thread overview]
Message-ID: <5062943C.5070006@doukki.net> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D235D17DD0E@SC-VEXCH4.marvell.com>

Le 24/09/2012 10:46, Prafulla Wadaskar a ?crit :
> 
> 
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de [mailto:u-boot-
>> bounces at lists.denx.de] On Behalf Of DrEagle
>> Sent: 22 September 2012 12:48
>> To: DrEagle
>> Cc: Lior Amsalem; u-boot at lists.denx.de; uboot at doukki.net
>> Subject: [U-Boot] [PATCH v2 4/5] Fix env address for Sheevaplug board
>>
>>
>> Fix env address for Sheevaplug board
>> Move env address and offset from 0x60000 to 0x80000
>>
>> Signed-off-by: drEagle <dreagle@doukki.net>
>> ---
>>  include/configs/sheevaplug.h |    5 ++---
>>  1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/configs/sheevaplug.h
>> b/include/configs/sheevaplug.h
>> index 7d710bf..a10e825 100644
>> --- a/include/configs/sheevaplug.h
>> +++ b/include/configs/sheevaplug.h
>> @@ -71,9 +71,8 @@
>>   * it has to be rounded to sector size
>>   */
>>  #define CONFIG_ENV_SIZE			0x20000	/* 128k */
>> -#define CONFIG_ENV_ADDR			0x60000
>> -#define CONFIG_ENV_OFFSET		0x60000	/* env starts here */
>> -
>> +#define CONFIG_ENV_ADDR			0x80000
>> +#define CONFIG_ENV_OFFSET		0x80000	/* env starts here */
> 
> Why do you need this shift?

Because the size of the new u-boot binary overlap the actual env offset.
If you reset the env or save env with a new u-boot, the code is corrupt, and noo boot anymore.

This shift fix this.

> Regards...
> Prafulla . .. 
> 

  reply	other threads:[~2012-09-26  5:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 10:15 [U-Boot] [PATCH 0/4] Marvell SDIO/MMC driver for Sheevaplug DrEagle
2012-09-22  7:15 ` [U-Boot] [PATCH v2 0/5] " DrEagle
2012-09-22  7:34   ` DrEagle
2012-09-24  8:50     ` Prafulla Wadaskar
2012-09-24  7:36   ` Prafulla Wadaskar
2012-09-24  8:48   ` Prafulla Wadaskar
2012-09-22  7:15 ` [U-Boot] [PATCH v2 1/5] Add Marvell SDIO/MMC driver for Kirkwood SoC DrEagle
2012-09-24  8:42   ` Prafulla Wadaskar
2012-09-22  7:16 ` [U-Boot] [PATCH v2 2/5] Add SDIO/MMC support for kirkwood SoC DrEagle
2012-09-24  8:44   ` Prafulla Wadaskar
2012-09-22  7:17 ` [U-Boot] [PATCH v2 3/5] Add SDIO/MMC support for Sheevaplug board DrEagle
2012-09-24  8:46   ` Prafulla Wadaskar
2012-09-22  7:18 ` [U-Boot] [PATCH v2 4/5] Fix env address " DrEagle
2012-09-24  8:46   ` Prafulla Wadaskar
2012-09-26  5:35     ` DrEagle [this message]
2012-09-26  7:33       ` Prafulla Wadaskar
2012-09-22  7:18 ` [U-Boot] [PATCH v2 5/5] Fix timeout in Marvell SDIO MMC driver DrEagle
2012-09-24  8:44   ` Prafulla Wadaskar

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=5062943C.5070006@doukki.net \
    --to=dreagle@doukki.net \
    --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