summaryrefslogtreecommitdiffstats
path: root/c/src/lib/libbsp/powerpc/mvme5500/README.irq
diff options
context:
space:
mode:
Diffstat (limited to 'c/src/lib/libbsp/powerpc/mvme5500/README.irq')
-rw-r--r--c/src/lib/libbsp/powerpc/mvme5500/README.irq20
1 files changed, 0 insertions, 20 deletions
diff --git a/c/src/lib/libbsp/powerpc/mvme5500/README.irq b/c/src/lib/libbsp/powerpc/mvme5500/README.irq
deleted file mode 100644
index fb31c4a5c3..0000000000
--- a/c/src/lib/libbsp/powerpc/mvme5500/README.irq
+++ /dev/null
@@ -1,20 +0,0 @@
-README.irq : Shuchen Kate Feng <feng1@bnl.gov>, Sept. 2, 2007
-
-As per implementation in shared PPC code,
-the BSPirqPrioTable[96] listed in irq_init.c is where the
-software developers can change the levels of priority
-for all the interrupts based on the need of their
-applications. The IRQs can be eanbled dynamically via the
-BSP_enable_pic_irq(), or disbaled dynamically via the
-BSP_disable_pic_irq().
-
-
-Support for run-time priority setup could be
-added easily, but there is no action taken yet due to concerns
-over computer security at VME CPU level.
-
-
-The software developers are forbidden to setup picIsrTable[],
-as it is a powerful engine for the BSP to find the pending
-highest priority IRQ at run time. It ensures the fastest/faster
-interrupt service to the highest/higher priority IRQ, if pending.