From f1865f4ca0fbfe30b47e030f0dc567e909203b68 Mon Sep 17 00:00:00 2001 From: patacongo Date: Fri, 20 Jan 2012 02:40:56 +0000 Subject: Fixes to PIC32 USB driver and LPC17xx CAN driver git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4316 7fd9a85b-ad96-42d3-883c-3090e2eb8679 --- nuttx/configs/sure-pic32mx/nsh/defconfig | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'nuttx/configs') diff --git a/nuttx/configs/sure-pic32mx/nsh/defconfig b/nuttx/configs/sure-pic32mx/nsh/defconfig index 18fe82631a..c4608022ba 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 -- cgit v1.2.3