summaryrefslogtreecommitdiffstats
path: root/doc/new_chapters
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-09-30 13:02:30 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-09-30 13:02:30 +0000
commit17408b901bc26f97aab23786801382d28b754231 (patch)
tree2f58989556bcaf95c14affb8334b0ebff5d22c50 /doc/new_chapters
parentMade cosmetic changes and documented routines in this file (diff)
downloadrtems-17408b901bc26f97aab23786801382d28b754231.tar.bz2
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 'doc/new_chapters')
0 files changed, 0 insertions, 0 deletions