path: root/make
diff options
authorJoel Sherrill <>1998-09-30 13:02:30 +0000
committerJoel Sherrill <>1998-09-30 13:02:30 +0000
commit17408b901bc26f97aab23786801382d28b754231 (patch)
tree2f58989556bcaf95c14affb8334b0ebff5d22c50 /make
parent982ed3f825f9afe0c8f8769b96ee53cfd54f6cd3 (diff)
Patch from Eric Norum <eric@skatter.USask.Ca>:
I found that my 68040/68360 test programs would not run even after I fixed the `wrong BSP' problem. It seems that there's a bug in the interrupt handling code for processors with hardware interrupt stacks (e.g. 68040). The wrong status register was getting pushed on the stack for the `return from exception' to call _ISR__Dispatch. This ended up making the context switch code run on the interrupt stack, so interrupt-driven context switches would always fail. I guess that no one has tried running any of the RTEMS-4.0 snapshots on a 68040 machine! Anyhow, here are the patches for 1) gen68360.cfg --- to fix the `wrong-BSP' problem. 2) m68k/cpu_asm.s --- to fix the hardware interrupt stack problem. With these patches in place, the network demo programs run on my 68040/68360 system. The paranoia program runs with no failures, defects nor flaws.
Diffstat (limited to 'make')
1 files changed, 0 insertions, 7 deletions
diff --git a/make/custom/gen68360.cfg b/make/custom/gen68360.cfg
index fb1493d788..cf2293f746 100644
--- a/make/custom/gen68360.cfg
+++ b/make/custom/gen68360.cfg
@@ -19,13 +19,6 @@ include $(RTEMS_ROOT)/make/custom/default.cfg
# This is the actual bsp directory used during the build process.
-## Target compiler config file, if any
-CONFIG.$(TARGET_ARCH).CC = $(RTEMS_ROOT)/make/compilers/gcc-target-default.cfg
-# We may install in a CPU model based directory but this is still
-# a gen68360 based bsp.
# You must use versions of gcc and gas that support the -mcpu32 option.