LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: MPC8560 util.S compilation error with E500 core support
Date: Tue, 24 Aug 2004 18:36:23 +0200	[thread overview]
Message-ID: <001301c489f8$82f426b0$5201a8c0@GEG2400> (raw)
In-Reply-To: 


Hi,

I first download a 2.6.7 Linux kernel to port it to a custom 8560 board.
The ./arch/ppc/boot/common/util.S compiles fine.

Then I download a 2.6.8 kernel. The same file util.S does not
compile any more because of "mtsrin" instruction not found with E500.

Between the 2 kernels, the -me500 option is distributed all over the
./arch/ppc directory. So the ./arch/ppc/boot is compiled with this option
and fails.

What is the right solution ?
Compile the boot whitout -me500 option or change util.S code ?

Thanks for any idea.
Gérard Guével


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-08-24 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 16:36 Gérard Guével [this message]
2004-08-24 18:00 ` MPC8560 util.S compilation error with E500 core support Kumar Gala

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='001301c489f8$82f426b0$5201a8c0@GEG2400' \
    --to=gguevel@interfaceconcept.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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