linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Stephen Cameron <steve.cameron@hp.com>
Cc: linuxppc-embedded@lists.linuxppc.org, Matt Porter <mporter@mvista.com>
Subject: Re: Unrecognized opcode: `mtdcr'
Date: Wed, 29 May 2002 12:05:44 -0700	[thread overview]
Message-ID: <20020529190544.GO5997@opus.bloom.county> (raw)
In-Reply-To: <20020529134822.A4429@zuul.cca.cpqcorp.net>


On Wed, May 29, 2002 at 01:48:22PM -0500, Stephen Cameron wrote:
>
> Hi,
>
> I just started trying to play with my new Ebony board...
>
> I noticed now 'as' complains: Unrecognized opcode: `mtdcr'
> when I do this:
> 	make ebony_config
[snip]
> But, if I do this:
> 	make walnut_config
[snip]
> Any ideas?

I think we need to change arch/ppc/Makefile from:
ifdef CONFIG_40x
CFLAGS := $(CFLAGS) -Wa,-m405
endif

To:
ifdef CONFIG_4xx
CFLAGS := $(CFLAGS) -Wa,-m405
endif

For the moment.  Until there's some 440-specific opcodes we use (are
there any?) which means we'll need to do -Wa,-m440.

Matt, do you want to do this or shall I?

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2002-05-29 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 18:48 Unrecognized opcode: `mtdcr' Stephen Cameron
2002-05-29 19:05 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 19:30 Cameron, Steve
2002-05-29 19:54 ` Tom Rini
2002-05-29 20:43   ` Matt Porter
2002-05-29 20:54     ` Matt Porter

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=20020529190544.GO5997@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mporter@mvista.com \
    --cc=steve.cameron@hp.com \
    /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;
as well as URLs for NNTP newsgroup(s).