public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support
Date: Tue, 25 Aug 2009 09:12:56 +0200	[thread overview]
Message-ID: <20090825091256.0fc009d2@marrow.netinsight.se> (raw)
In-Reply-To: <20090824100154.2E9AB833DBD2@gemini.denx.de>

On Mon, 24 Aug 2009 12:01:54 +0200
Wolfgang Denk <wd@denx.de> wrote:

> Dear Simon Kagstrom,
> 
> In message <20090824105935.038bd229@marrow.netinsight.se> you wrote:
> > 
> > I updated my git tree today and got this patch (among other things). It
> > does not work very well for me, unfortunately. I've tried three
> > toolchains (4.3.3, 4.3.4, 4.4.1) built with crosstool-ng, and all of
> > them build an image which doesn't run correct.
> 
> Hm... aren't there known issues with these compiler versions on ARM?

Small update: I've tried with the ELDK toolchains 4.1 and 4.2
(2007-01-21 and 2008-11-24). Both these fail as well, albeit in a
slightly different way. The printfs are correct, but 4.2 still has the
nand_bbt issue:

  U-Boot 2009.08-rc3-00013-g853ae64 (Aug 25 2009 - 08:28:05)
  Marvell-OpenRD_base

  SoC:   Kirkwood 88F6281_A0
  DRAM:  512 MB
  NAND:  512 MiB
  nand_bbt: Can't scan flash and build the RAM-based BBT
  Net:   egiga0
  88E1116 Initialized on egiga0
  Hit any key to stop autoboot:  0 
  Marvell>> 

The 4.1 version just hangs on the NAND printout. I've tested both with
USE_PRIVATE_LIBGCC=yes and USE_PRIVATE_LIBGCC unset, and get the same
results.

// Simon

  parent reply	other threads:[~2009-08-25  7:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 11:17 [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support Wolfgang Denk
2009-08-17 13:00 ` Tom
2009-08-17 13:25   ` Wolfgang Denk
2009-08-17 15:26   ` Dirk Behme
2009-08-17 19:43 ` ksi at koi8.net
2009-08-17 20:17 ` Magnus Lilja
2009-08-17 20:27   ` Wolfgang Denk
2009-08-18 17:08     ` Magnus Lilja
2009-08-18 21:18       ` Wolfgang Denk
2009-08-18 11:06 ` Gaye Abdoulaye Walsimou
2009-08-18 11:22   ` Wolfgang Denk
2009-08-20 15:27   ` Andrzej Wolski
2009-08-18 11:45 ` Gaye Abdoulaye Walsimou
2009-08-18 18:50 ` Tom
2009-08-18 21:19   ` Wolfgang Denk
2009-08-21 21:12 ` Wolfgang Denk
2009-08-24  8:59   ` Simon Kagstrom
2009-08-24 10:01     ` Wolfgang Denk
2009-08-24 11:28       ` Prafulla Wadaskar
2009-08-24 11:56         ` Wolfgang Denk
2009-08-24 12:41           ` Prafulla Wadaskar
2009-08-24 12:59             ` Simon Kagstrom
2009-08-24 13:05             ` Wolfgang Denk
2009-08-24 11:38       ` Simon Kagstrom
2009-08-24 12:01         ` Wolfgang Denk
2009-08-24 12:49           ` Simon Kagstrom
2009-08-25  7:12       ` Simon Kagstrom [this message]
2009-09-04 20:05         ` Wolfgang Denk
2009-09-07  6:23           ` Simon Kagstrom
2009-09-07  8:59             ` Prafulla Wadaskar
2009-09-07  9:15               ` Simon Kagstrom

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=20090825091256.0fc009d2@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --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