From 0cd687a4d6b8d1242690ec32c378ffd5eaccb951 Mon Sep 17 00:00:00 2001
From: Greg Ungerer <gerg@snapgear.com>
Date: Mon, 26 Jun 2006 10:33:10 +1000
Subject: [PATCH] --- yaml --- r: 30162 b: refs/heads/master c:
 5503967307f3fa443f5770a4df5ea4fbe9fb3917 h: refs/heads/master v: v3

---
 [refs]                                      |  2 +-
 trunk/arch/m68knommu/platform/532x/Makefile | 20 ++++++++++++++++++++
 2 files changed, 21 insertions(+), 1 deletion(-)
 create mode 100644 trunk/arch/m68knommu/platform/532x/Makefile

diff --git a/[refs] b/[refs]
index 54b6c64ac116..0fb49cd19a3a 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: f3dd71209472b93340c1a940cc832c2712307b3e
+refs/heads/master: 5503967307f3fa443f5770a4df5ea4fbe9fb3917
diff --git a/trunk/arch/m68knommu/platform/532x/Makefile b/trunk/arch/m68knommu/platform/532x/Makefile
new file mode 100644
index 000000000000..12301803b9eb
--- /dev/null
+++ b/trunk/arch/m68knommu/platform/532x/Makefile
@@ -0,0 +1,20 @@
+#
+# 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:
+#
+# EXTRA_CFLAGS += -DTRAP_DBG_INTERRUPT
+# EXTRA_AFLAGS += -DTRAP_DBG_INTERRUPT
+#
+
+ifdef CONFIG_FULLDEBUG
+AFLAGS += -DDEBUGGER_COMPATIBLE_CACHE=1
+endif
+
+#obj-y := config.o usb-mcf532x.o spi-mcf532x.o
+obj-y := config.o