summaryrefslogtreecommitdiff
path: root/nuttx/ChangeLog
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-10-30 17:34:13 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-10-30 17:34:13 +0000
commitb4ef55c32f0a6c45854a33fb560993b71cab420f (patch)
tree60d2b539f8aeb3e7ea4f9cea76a83f70d82de479 /nuttx/ChangeLog
parent428f80ef022344e6f185298e44ae06cb87f81145 (diff)
downloadnuttx-b4ef55c32f0a6c45854a33fb560993b71cab420f.tar.gz
nuttx-b4ef55c32f0a6c45854a33fb560993b71cab420f.tar.bz2
nuttx-b4ef55c32f0a6c45854a33fb560993b71cab420f.zip
upate
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2196 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/ChangeLog')
-rw-r--r--nuttx/ChangeLog6
1 files changed, 5 insertions, 1 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index ca3bdb9a7..644275e54 100644
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -942,4 +942,8 @@
back to the HSI (internal clock), and the system clock is too slow by a
factor of 11.1%. This was fixed by simply add the volatile storage class
to the timeout loop counter
-
+ * arch/arm/src/stm32/stm32_irq.c - Fixed a critical bug in the interrupt
+ control logic. The wrong register was being used for interrupts in a
+ certain range. Worked fine until you try to use an interrupt in that
+ range!
+