public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Gary Jennejohn <garyj@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH V2] Add the Harris QUAD100HD AMCC 405EP-based board.
Date: Mon, 28 Apr 2008 11:32:29 +0200	[thread overview]
Message-ID: <20080428113229.6510c91c@peedub.jennejohn.org> (raw)
In-Reply-To: <200804271401.45781.sr@denx.de>

On Sun, 27 Apr 2008 14:01:45 +0200
Stefan Roese <sr@denx.de> wrote:

> On Saturday 26 April 2008, Gary Jennejohn wrote:
> > > > +#define CFG_MONITOR_LEN		(256 * 1024)	/* Reserve 256 kB for Monitor	*/
> > > > +#define CFG_MALLOC_LEN		(128 * 1024)	/* Reserve 128 kB for malloc()	*/
> > > > +#define CFG_MONITOR_BASE	0xFFF80000
> > >
> > > CFG_MONITOR_BASE at 0xfff80000 makes me think that the U-Boot image has a
> > > size of 512k. But CFG_MONITOR_LEN is 256k. Which one is correct? I would
> > > think that 256k should be enough for this image.
> >
> > That's a valid point.  Actually u-boot.bin is 512kB in length, but only
> > because there's a reset vector at 0xFFFFFFFC.  u-boot itself is really
> > only 256kB in size.
> >
> > So now I wonder - what's correct?  If CFG_MONITOR_LEN applies to RAM,
> > which it seems to since it only really affects TOTAL_MALLOC_LEN, then
> > 256kB is correct and no change is required.
> 
> I would change the image size to 256k to safe some space in FLASH. For this 
> you have to change TEXT_BASE (in config.mk in your board directory) to 
> 0xfffc0000. And CFG_MONITOR_BASE too. Or even better:
> 
> #define CFG_MONITOR_BASE        (TEXT_BASE)
> 

Well, I took these values from PPCBoot, as used by the customer, and I
see no technical reason to change these values with which the customer
is obviously satisfied.

---
Gary Jennejohn
*********************************************************************
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
*********************************************************************

  reply	other threads:[~2008-04-28  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 16:04 [U-Boot-Users] [PATCH V2] Add the Harris QUAD100HD AMCC 405EP-based board Gary Jennejohn
2008-04-26  6:22 ` Stefan Roese
2008-04-26 10:18   ` Gary Jennejohn
2008-04-27 12:01     ` Stefan Roese
2008-04-28  9:32       ` Gary Jennejohn [this message]
2008-04-28  9:40         ` Stefan Roese
2008-04-28 10:05         ` Wolfgang Denk
2008-04-28 11:11           ` Gary Jennejohn
2008-04-26 13:11   ` Wolfgang Grandegger
2008-04-27 12:07     ` Stefan Roese
2008-04-27 21:41       ` Wolfgang Denk
2008-04-28  9:45         ` Stefan Roese
2008-04-28  9:40       ` Gary Jennejohn
2008-04-27 21:37     ` Wolfgang Denk

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=20080428113229.6510c91c@peedub.jennejohn.org \
    --to=garyj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox