public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] AT91SAM9*: Change kernel address in dataflash to match u-boot's size
Date: Mon, 09 Apr 2012 08:36:15 +0200	[thread overview]
Message-ID: <4F82835F.2030201@googlemail.com> (raw)
In-Reply-To: <20120408200641.76D21202B18@gemini.denx.de>

Dear Wolfgang,

On 08.04.12 22:06, Wolfgang Denk wrote:
> Dear Alexandre Belloni,
> 
> In message <1333909023-6725-1-git-send-email-alexandre.belloni@piout.net> you wrote:
>> On at91sam platforms, u-boot grew larger than the allocated size in
>> dataflash, the layout was:
>> bootstrap  0x00000000
>> ubootenv   0x00004200
>> uboot      0x00008400
>> kernel     0x00042000
>>
>> u-boot with the defconfig doesn't seem to fit in 0x42000 - 0x8400 =
>> 0x39C00 bytes anymore.
>>
>> Now, the layout is:
>> bootstrap  0x00000000
>> ubootenv   0x00004200
>> uboot      0x00008400
>> kernel     0x00084000
> 
> Where are these odd sizes like
> 
>>  #define CONFIG_ENV_SIZE		0x4200
> 
> coming from?  Has a size of 0x4200 any special maning on these
> systems?

please read Ulfs mail:
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/123862/focus=125897

I think it is OK to apply this patch.
All these atmel boards need some more attention (lack of maintainer).
Reinhard started to migrate a lot of stuff but unfortunately this
process is not completely finished. I will not say it is left undone but
there is still a lot to do.
I think another point is that these Atmel devices became less important
than before in U-Boot (I see not really much users here even though a
lot of people use it):
 a) a lot of users favor the at91bootstrap SPL to boot linux (no need
for u-boot)
 b) they have well-hung cores

best regards

Andreas Bie?mann

PS: besides a) there was a user in irc around Christmas who count 'the
SPL for atmel devices in U-Boot' a good idea. He said he wants to play
with it ... I wonder if he does.

  reply	other threads:[~2012-04-09  6:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 21:37 [U-Boot] [PATCH v2] Change kernel address in dataflash to match u-boot's size Alexandre Belloni
2012-02-18 15:13 ` Albert ARIBAUD
2012-02-18 16:21   ` Albert ARIBAUD
2012-02-20 10:40     ` Alexandre Belloni
2012-02-20 10:46       ` Albert ARIBAUD
2012-02-20 12:48         ` [U-Boot] [PATCH] AT91SAM9*: " Alexandre Belloni
2012-02-20 13:00           ` Albert ARIBAUD
2012-02-20 16:40             ` [U-Boot] [PATCH v3] " Alexandre Belloni
2012-02-27 15:25               ` Ulf Samuelsson
2012-02-28 22:57                 ` Alexandre Belloni
2012-02-29  0:50                   ` Ulf Samuelsson
2012-02-29  8:58                     ` Alexandre Belloni
2012-02-29  9:49                       ` Ulf Samuelsson
2012-04-08 18:17                         ` [U-Boot] [PATCH v4] " Alexandre Belloni
2012-04-08 20:06                           ` Wolfgang Denk
2012-04-09  6:36                             ` Andreas Bießmann [this message]
2012-04-09  8:15                               ` Wolfgang Denk
2012-04-17 23:26                                 ` Ulf Samuelsson
2012-04-21 21:19                                   ` Alexandre Belloni
2012-02-20 12:51         ` [U-Boot] [PATCH v2] " Alexandre Belloni

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=4F82835F.2030201@googlemail.com \
    --to=andreas.devel@googlemail.com \
    --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