Fixes to PIC32 USB driver and LPC17xx CAN driver

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4316 42af7a65-404d-4744-a932-0658087f49c3

1 files changed, 0 insertions, 12 deletions

diff --git a/nuttx/configs/sure-pic32mx/nsh/defconfig b/nuttx/configs/sure-pic32mx/nsh/defconfig
index 18fe82631..c4608022b 100644
--- a/nuttx/configs/sure-pic32mx/nsh/defconfig
+++ b/nuttx/configs/sure-pic32mx/nsh/defconfig
@@ -67,18 +67,6 @@
 #   relationship to interrupt vectors. In such cases, CONFIG_ARCH_VECNOTIRQ
 #   must defined so that the OS logic will know not to assume it can use
 #   a vector number to enable or disable interrupts.
-# CONFIG_ARCH_NOINTC - define if the architecture does not
-#   support an interrupt controller or otherwise cannot support
-#   APIs like up_enable_irq() and up_disable_irq().
-# CONFIG_ARCH_VECNOTIRQ - Usually the interrupt vector number provided
-#   to interfaces like irq_attach() and irq_detach are the same as IRQ
-#   numbers that are provied to IRQ management functions like
-#   up_enable_irq() and up_disable_irq().  But that is not true for all
-#   interrupt controller implementations.  For example, the PIC32MX
-#   interrupt controller manages interrupt sources that have a many-to-one
-#   relationship to interrupt vectors. In such cases, CONFIG_ARCH_VECNOTIRQ
-#   must defined so that the OS logic will know not to assume it can use
-#   a vector number to enable or disable interrupts.
 # CONFIG_ARCH_IRQPRIO - The PIC32MX supports interrupt prioritization
 # CONFIG_ARCH_INTERRUPTSTACK - This architecture supports an interrupt
 #   stack. If defined, this symbol is the size of the interrupt