From 3382a9f4f709e55918c21a95fc2e91cd52f53918 Mon Sep 17 00:00:00 2001 From: Greg Ungerer Date: Fri, 9 Sep 2005 09:32:14 +1000 Subject: [PATCH] --- yaml --- r: 8017 b: refs/heads/master c: 97591b2c76e3a11d6060b72aa53dc30d3d5478c5 h: refs/heads/master i: 8015: 8f9f65d85fdcfb441ddc7b76394983594003ff3b v: v3 --- [refs] | 2 +- trunk/arch/m68knommu/platform/523x/Makefile | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 trunk/arch/m68knommu/platform/523x/Makefile diff --git a/[refs] b/[refs] index 5abea1d9d0b2..210c23856054 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 1bdd89db117a55c77a854829ff507d6d68ab6485 +refs/heads/master: 97591b2c76e3a11d6060b72aa53dc30d3d5478c5 diff --git a/trunk/arch/m68knommu/platform/523x/Makefile b/trunk/arch/m68knommu/platform/523x/Makefile new file mode 100644 index 000000000000..c1578b016160 --- /dev/null +++ b/trunk/arch/m68knommu/platform/523x/Makefile @@ -0,0 +1,19 @@ +# +# 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