[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7877.1283507577@redhat.com>
Date: Fri, 03 Sep 2010 10:52:57 +0100
From: David Howells <dhowells@...hat.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: dhowells@...hat.com, Greg Ungerer <gerg@...pgear.com>,
Andreas Schwab <schwab@...hat.com>, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] M68K: Use CONFIG_MMU not __uClinux__ to select m68knommu contributions
Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > Not sure about m68k but m68knommu targets already setup
> > appropriate -mcpu flags for its various supported CPU types.
>
> Same for m68k.
It doesn't seem to:
warthog>grep -r mcpu arch/m68k
warthog1>grep -r mtune arch/m68k
warthog1>
I see that m68knommu does:
warthog1>grep -r mcpu arch/m68knommu/
arch/m68knommu/Makefile:cflags-$(CONFIG_M5206) := $(call cc-option,-mcpu=5206,-m5200)
arch/m68knommu/Makefile:cflags-$(CONFIG_M520x) := $(call cc-option,-mcpu=5208,-m5200)
arch/m68knommu/Makefile:cflags-$(CONFIG_M523x) := $(call cc-option,-mcpu=523x,-m5307)
...
I guess the m68k compiler I already had doesn't fully support -m5200, since I
see that, but it doesn't compile some of the instructions when compiling the
m68knommu defconfig (CONFIG_M520x=y).
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists