public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] sbc8641d: misc fixes and generic board enablement
Date: Sat, 17 Oct 2015 18:50:26 -0400	[thread overview]
Message-ID: <20151017225026.GT26878@windriver.com> (raw)
In-Reply-To: <20151017215021.GV23893@bill-the-cat>

[Re: [PATCH 0/6] sbc8641d: misc fixes and generic board enablement] On 17/10/2015 (Sat 17:50) Tom Rini wrote:

> On Sat, Oct 17, 2015 at 04:40:25PM -0400, Paul Gortmaker wrote:
> 
> > The sbc8641d is not really a state of the art board anymore, but it
> > does have the distinctive feature of being one of the relatively few
> > SMP powerpc boards around.  Combined with its small form factor, it
> > remains a useful testing platform.  So here we enable the generic
> > board support so that it can remain in tree.
> > 
> > It turns out that in bringing the board forward, we've run into the
> > size limit for the image, due to inevitable expansion, which led
> > to some odd testing behaviour, depending on .config settings etc.
> > Here we increase the image space from two 128k sectors to three,
> > so we should be good for as long as the board remains relevant now.
> 
> Thanks for finding this.  I am going to grab this for the release and I
> might re-word a commit or two.  I have one ask tho, can you look at
> using CONFIG_BOARD_SIZE_LIMIT, perhaps in a generic way so that we catch
> more "oops, the board grew too big, run-time now will fail!" issues?

Yeah, I'll have a look -- I was kind of surprised that it didn't scream at
me when this happened during the build, since I'd think we have all the
information at our fingertips to do a build bug on or similar, and I
can't be the 1st one bitten by this.

P.
--

> 
> -- 
> Tom

  reply	other threads:[~2015-10-17 22:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 20:40 [U-Boot] [PATCH 0/6] sbc8641d: misc fixes and generic board enablement Paul Gortmaker
2015-10-17 20:40 ` [U-Boot] [PATCH v2 1/6] sbc8641d: enable command line editing Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot,v2,1/6] " Tom Rini
2015-10-17 20:40 ` [U-Boot] [PATCH v2 2/6] sbc8641d: increase malloc pool size to a sane default Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-10-17 20:40 ` [U-Boot] [PATCH v2 3/6] sbc8641d: set proper environment sector size Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-10-17 20:40 ` [U-Boot] [PATCH v2 4/6] sbc8641d: add basic flash setup instructions to README file Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-10-17 20:40 ` [U-Boot] [PATCH v2 5/6] sbc8641d: enable and test CONFIG_SYS_GENERIC_BOARD Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-10-20 14:49     ` Paul Gortmaker
2015-10-17 20:40 ` [U-Boot] [PATCH v2 6/6] sbc8641d: increase monitor size from 256k to 384k Paul Gortmaker
2015-10-20  0:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-10-17 21:50 ` [U-Boot] [PATCH 0/6] sbc8641d: misc fixes and generic board enablement Tom Rini
2015-10-17 22:50   ` Paul Gortmaker [this message]
2015-10-17 23:11     ` Paul Gortmaker
2015-10-17 23:58       ` Tom Rini

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=20151017225026.GT26878@windriver.com \
    --to=paul.gortmaker@windriver.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