[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4863E414.4090303@seznam.cz>
Date: Thu, 26 Jun 2008 20:46:44 +0200
From: Michal Simek <monstr@...nam.cz>
To: Adrian Bunk <bunk@...nel.org>
CC: monstr@...nam.cz, linux-kernel@...r.kernel.org, arnd@...db.de,
linux-arch@...r.kernel.org, stephen.neuendorffer@...inx.com,
John.Linn@...inx.com, john.williams@...alogix.com, matthew@....cx,
will.newton@...il.com, drepper@...hat.com,
microblaze-uclinux@...e.uq.edu.au, grant.likely@...retlab.ca,
linuxppc-dev@...abs.org, vapier.adi@...il.com,
alan@...rguk.ukuu.org.uk, hpa@...or.com
Subject: Re: [PATCH 02/60] microblaze_v4: Makefiles for Microblaze cpu
Adrian Bunk napsal(a):
> On Thu, Jun 26, 2008 at 02:29:31PM +0200, monstr@...nam.cz wrote:
>> ...
>> --- /dev/null
>> +++ b/arch/microblaze/Makefile
>> ...
>> +# Work out HW multipler support. This is icky.
>> +# 1. Spartan2 has no HW multiplers.
>> +# 2. MicroBlaze v3.x always uses them, except in Spartan 2
>> +# 3. All other FPGa/CPU ver combos, we can trust the CONFIG_ settings
>> +ifeq (,$(findstring spartan2,$(CONFIG_XILINX_MICROBLAZE0_FAMILY)))
>> + ifeq ($(CPU_MAJOR),3)
>> + CPUFLAGS-1 += -mno-xl-soft-mul
>> + else
>> + # USE_HW_MUL can be 0, 1, or 2, defining a heirarchy of HW Mul support.
>> + CPUFLAGS-$(subst 1,,$(CONFIG_XILINX_MICROBLAZE0_USE_HW_MUL)) += -mxl-multiply-high
>> + CPUFLAGS-$(CONFIG_XILINX_MICROBLAZE0_USE_HW_MUL) += -mno-xl-soft-mul
>> + endif
>> +endif
>> +CPUFLAGS-$(CONFIG_XILINX_MICROBLAZE0_USE_DIV) += -mno-xl-soft-div
>> +CPUFLAGS-$(CONFIG_XILINX_MICROBLAZE0_USE_BARREL) += -mxl-barrel-shift
>> +CPUFLAGS-$(CONFIG_XILINX_MICROBLAZE0_USE_PCMP) += -mxl-pattern-compare
>> +
>> +CPUFLAGS-1 += $(call cc-option,-mcpu=v$(CPU_VER))
>> +
>> +# The various CONFIG_XILINX cpu features options are integers 0/1/2...
>> +# rather than bools y/n
>> +CFLAGS += $(CPUFLAGS-1)
>> +CFLAGS += $(CPUFLAGS-2)
>> ...
>
> Why are the options not bools?
>
> cu
> Adrian
because CONFIG_XILINX_... are 0, 1 or 2 not only y, n.
M
--
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