From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Cannot assemble cpu/ppc4xx/start.S for sequoia
Date: Thu, 21 Jun 2007 13:52:45 +0200 [thread overview]
Message-ID: <200706211352.45338.sr@denx.de> (raw)
In-Reply-To: <467A781F.268B.006F.0@netstal.com>
Hi Niklaus,
On Thursday 21 June 2007, Niklaus Giger wrote:
> After pulling the recent git merges from stefan I get the following error:
>
> ppc_4xx-gcc -D__ASSEMBLY__ -g -Os -fPIC -ffixed-r14 -meabi
> -fno-strict-aliasing -D__KERNEL__ -DTEXT_BASE=0xFFFA0000
> -I/home/ng/u-boot/build.sequoia/include2
> -I/home/ng/u-boot/build.sequoia/include
> -I/home/ng/u-boot/u-boot.work/include -fno-builtin -ffreestanding -nostdinc
> -isystem /home/hcu/eldk-4.1/usr/bin/../lib/gcc/powerpc-linux/4.0.0/include
> -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29
> -mstring -msoft-float -Wa,-m405 -mcpu=405 -DCONFIG_440=1 -c -o
Hmmm. CONFIG_440 is set _and_ cpu=405. This is the source of the problem.
> /home/ng/u-boot/build.sequoia/cpu/ppc4xx/start.o start.S
> start.S: Assembler messages:
> start.S:1211: Error: Unrecognized opcode: `rfmci'
Is this a PPC405 based board or a PPC440 based board? Please include your
board config file and I'll take a look at it.
As you may have noticed all 4xx boards (405 & 440) compile clean with ELDK4.0.
Viele Gr??e,
Stefan
=====================================================================
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
=====================================================================
next prev parent reply other threads:[~2007-06-21 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:07 [U-Boot-Users] Cannot assemble cpu/ppc4xx/start.S for sequoia Niklaus Giger
2007-06-21 11:52 ` Stefan Roese [this message]
2007-06-21 11:53 ` Rafal Jaworowski
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=200706211352.45338.sr@denx.de \
--to=sr@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