public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EABI Problem
Date: Tue, 06 Nov 2007 08:33:48 +0100	[thread overview]
Message-ID: <20071106073348.EDED6249E7@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 06 Nov 2007 06:31:12 +0100." <200711060631.12189.sr@denx.de>

In message <200711060631.12189.sr@denx.de> you wrote:
>
> > > > -#define CFG_MALLOC_LEN	(CFG_ENV_SIZE + 128*1024)
> > > > +#define CFG_MALLOC_LEN	(128*1024)
...
> > > see why this change would be needed. If there is a compi8le  problem,
> > > the  reason  for  that  problem  should be located and fixed, without
> > > changing this code.
...
> > Well ARM assembly only accepts immediate values with certain
> > properties (representable as an 8-bit value plus a 5-bit shift
> > or something, I forgot the details). My ARM assembly skills

My gut feeling is that this is not the root of the  problem.  I  feel
that probably the assembler does not see a pure numerical expression,
but  instead  is  confronted  with the (unsubstituted) string literal
CFG_ENV_SIZE, and that this is causing the problem.

This is what I think needs to be checked and fixed, as the same
problem might be present (eventually undetected) somewhere else, too.

> > are pretty weak, so changing start.S to accept an arbitrary constant
> > is out of scope for me. We could maybe just set CFG_MALLOC_LEN
> > to 132*1024 (untested), or we could move the CFG_MALLOC_LEN
> > down in the file next to the

Please try out if "(132*1024)" works... that would give a some
helpful additional information.

> > #ifdef CONFIG_KB9202
> > #define CFG_ENV_OFFSET                  0x3E00
> > #define CFG_ENV_SIZE                    0x0200

This is broken. 512 bytes of environmnt is much too small to be
useful.

> > #define CFG_MALLOC_LEN	(CFG_ENV_SIZE + 128*1024 + 0x4e00)

This is broken,too. Where is the 0x4e00 coming from here?

> > #else
> > #define CFG_ENV_OFFSET                  0x1000
> > #define CFG_ENV_SIZE                    0x1000
> > #define CFG_MALLOC_LEN	(CFG_ENV_SIZE + 128*1024 + 0x3000)

Where is the 0x3000 coming from here?

> Why not just increasing. It's normally no problem having bigger malloc area:
> 
> #define CFG_MALLOC_LEN	(256*1024)

If this works, then it is another indication that there is a
preprocessing problem. This problem should be fixed and not hidden.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Houston, Tranquillity Base here.  The Eagle has landed.
                                                    -- Neil Armstrong

  reply	other threads:[~2007-11-06  7:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 16:02 [U-Boot-Users] EABI Problem Russ Ferriday
2007-11-02 15:37 ` Johannes Stezenbach
2007-11-05 16:18   ` Johannes Stezenbach
2007-11-05 19:26     ` Wolfgang Denk
2007-11-05 21:25       ` Johannes Stezenbach
2007-11-06  5:31         ` Stefan Roese
2007-11-06  7:33           ` Wolfgang Denk [this message]
2007-11-06 13:30             ` Philip Balister
2007-11-16 20:39         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-07-05 17:11 [U-Boot-Users] EABI problem Patrice Vilchez
2007-07-06 13:29 ` Peter Pearse
2007-07-06 13:45   ` Patrice Vilchez
2007-07-06 14:02     ` Philip Balister
2007-07-06 14:15       ` Patrice Vilchez
2007-07-06 14:22         ` Philip Balister
2007-07-06 14:33           ` Patrice Vilchez

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=20071106073348.EDED6249E7@gemini.denx.de \
    --to=wd@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