public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] mpq101: initial support for Mercury Computer Systems MPQ101 board
Date: Wed, 12 Jan 2011 18:42:48 -0800 (PST)	[thread overview]
Message-ID: <811305.36830.qm@web37607.mail.mud.yahoo.com> (raw)
In-Reply-To: <20110111074337.65517150A49@gemini.denx.de>

> > 
> > 1. I want to fit an environment and the bootloader
> into a single flash
> > sector.
> 
> This is a very bad idea as it will open a window brick your
> system at
> each and every "saveenv" command.
> 
> I strongly recommend not to do that.

This issue is well understood.
Yet, we are talking an industrial mezzanine card here, of variety which
is put into the (ups-backed in most cases) rack once and forgotten.

If it was a consumer or developer oriented device, I, of course, would
use a safer approach. From what I've seen, this is more or less in line
with many other boards already supported by u-boot.

> 
> If you stop doing 1., all other problems will just
> disappear.

Unfortunately, these boards have flash chips without small boot blocks,
and considering the nature of typical board usage (as described) vs
value of some additional flash space, I see it as a reasonable trade-off.

> 
> 
> If you really insist in such an unreliablke configuration,
> a custom
> linker script would IMO be better, as it would make the
> image layout
> more visible.

Typical ld script is rather largish with many details of no direct
relevance to any specific board. Single flag modifying the section offset
has the advantage of being concise and immediately visible.

I will, of course, look at it again.



      

  reply	other threads:[~2011-01-13  2:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  6:22 [U-Boot] [PATCH] mpq101: initial support for Mercury Computer Systems MPQ101 board Alex Dubov
2010-12-27 12:12 ` Wolfgang Denk
2010-12-28  4:42   ` Alex Dubov
2011-01-10 22:43     ` Wolfgang Denk
2011-01-11  3:14       ` Alex Dubov
2011-01-11  5:43         ` Wolfgang Denk
2011-01-11  7:32           ` Alex Dubov
2011-01-17 22:38             ` Wolfgang Denk
2011-01-18  4:32               ` Kumar Gala
2010-12-28  5:53   ` Alex Dubov
2011-01-10 22:49     ` Wolfgang Denk
2011-01-07  7:16   ` [U-Boot] [PATCH v3] " Alex Dubov
2011-01-10 22:56     ` Wolfgang Denk
2011-01-11  2:44       ` Alex Dubov
2011-01-11  7:43         ` Wolfgang Denk
2011-01-13  2:42           ` Alex Dubov [this message]
2011-01-14  9:10       ` [U-Boot] [PATCH v4] " Alex Dubov
2011-01-14 11:49         ` Kumar Gala
2011-01-17  3:07           ` Alex Dubov
2011-01-17  7:26           ` [U-Boot] [PATCH v5] " Alex Dubov
2011-01-18  5:15             ` Kumar Gala
2011-01-18  8:03               ` [U-Boot] [PATCH v6] " Alex Dubov
2011-01-18  9:42                 ` Kumar Gala
2011-01-19  9:50                   ` Alex Dubov
2011-01-20  5:02                   ` [U-Boot] [PATCH v7] " Alex Dubov
2011-01-20  7:50                     ` Kumar Gala
2011-01-24  5:59                       ` [U-Boot] [PATCH v8] " Alex Dubov
2011-01-27  5:45                         ` Kumar Gala
2011-01-27  8:41                           ` Alex Dubov
2011-01-20  8:46                     ` [U-Boot] [PATCH v7] " Wolfgang Denk
2011-01-22  7:27                       ` Alex Dubov
2011-01-14 11:51         ` [U-Boot] [PATCH v4] " Kumar Gala

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=811305.36830.qm@web37607.mail.mud.yahoo.com \
    --to=oakad@yahoo.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