m68knommu: move the 532x platform code into the common ColdFire code directory
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <gerg@uclinux.org>
This commit is contained in:
parent
9f8c8c072d
commit
e33e73f560
|
@ -115,7 +115,6 @@ core-$(CONFIG_M68000) += arch/m68k/platform/68328/
|
|||
core-$(CONFIG_M68EZ328) += arch/m68k/platform/68EZ328/
|
||||
core-$(CONFIG_M68VZ328) += arch/m68k/platform/68VZ328/
|
||||
core-$(CONFIG_COLDFIRE) += arch/m68k/platform/coldfire/
|
||||
core-$(CONFIG_M532x) += arch/m68k/platform/532x/
|
||||
core-$(CONFIG_M54xx) += arch/m68k/platform/54xx/
|
||||
|
||||
|
||||
|
|
|
@ -1,18 +0,0 @@
|
|||
#
|
||||
# Makefile for the m68knommu linux kernel.
|
||||
#
|
||||
|
||||
#
|
||||
# If you want to play with the HW breakpoints then you will
|
||||
# need to add define this, which will give you a stack backtrace
|
||||
# on the console port whenever a DBG interrupt occurs. You have to
|
||||
# set up you HW breakpoints to trigger a DBG interrupt:
|
||||
#
|
||||
# ccflags-y := -DTRAP_DBG_INTERRUPT
|
||||
# asflags-y := -DTRAP_DBG_INTERRUPT
|
||||
#
|
||||
|
||||
asflags-$(CONFIG_FULLDEBUG) := -DDEBUGGER_COMPATIBLE_CACHE=1
|
||||
|
||||
#obj-y := config.o usb-mcf532x.o spi-mcf532x.o
|
||||
obj-y := config.o
|
|
@ -24,7 +24,7 @@ obj-$(CONFIG_M527x) += m527x.o pit.o intc-2.o reset.o
|
|||
obj-$(CONFIG_M5272) += m5272.o intc-5272.o timers.o
|
||||
obj-$(CONFIG_M528x) += m528x.o pit.o intc-2.o reset.o
|
||||
obj-$(CONFIG_M5307) += m5307.o timers.o intc.o reset.o
|
||||
obj-$(CONFIG_M532x) += timers.o intc-simr.o reset.o
|
||||
obj-$(CONFIG_M532x) += m532x.o timers.o intc-simr.o reset.o
|
||||
obj-$(CONFIG_M5407) += m5407.o timers.o intc.o reset.o
|
||||
obj-$(CONFIG_M54xx) += sltimers.o intc-2.o
|
||||
|
||||
|
|
Loading…
Reference in a new issue