summaryrefslogtreecommitdiff
path: root/nuttx/ChangeLog
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-11-04 20:54:18 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2009-11-04 20:54:18 +0000
commitdeab3d6e8ea2a6f4e4cb4f14927e660b5b56156b (patch)
tree162adc3f04283327b9f14b5319ebb92b345bcd00 /nuttx/ChangeLog
parentb8a493effbfca3d70be0c454a0a173380ae65efa (diff)
downloadnuttx-deab3d6e8ea2a6f4e4cb4f14927e660b5b56156b.tar.gz
nuttx-deab3d6e8ea2a6f4e4cb4f14927e660b5b56156b.tar.bz2
nuttx-deab3d6e8ea2a6f4e4cb4f14927e660b5b56156b.zip
Prep for 0.4.13 releasenuttx-4.13
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2225 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/ChangeLog')
-rw-r--r--nuttx/ChangeLog10
1 files changed, 5 insertions, 5 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index c4e0f0c43..73ac116cc 100644
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -913,7 +913,7 @@
LCD driver and NX bringup on the eval board's display and MicroSD support. An SPI
driver was included in the 0.4.12 release, but is not yet tested.
-0.4.13 2009-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>
+0.4.13 2009-11-04 Gregory Nutt <spudmonkey@racsa.co.cr>
* include/nuttx/mtd.h. Added a simple interface definition to support some
FLASH, EEPROM, NVRAM, etc. devices.
@@ -932,10 +932,9 @@
* arch/arm/src/stm32/ - You have to configure CTS/RTS function pins for USART
2 and USART 3 even if you are not using flow control.
* arch/arm/src/stm32/stm32_usbdev.c - Added a USB device-side driver for the
- STM32.
-
- NOTE: This STM32 USB driver is not yet fully untested
-
+ STM32. NOTE: This is an early release of the USB driver. There is at least
+ one known issue. The examples/usbserial test only executes correctly under
+ certain conditions (see the full bug description in the TODO list).
* arch/arm/src/stm32/stm32_rcc.c - Fixed an error in clock initialization.
On some boards (none of mine), the HSE (high speed external clock) delay
loop times out if the optimization level is high. The STM32 then falls
@@ -947,3 +946,4 @@
certain range. Worked fine until you try to use an interrupt in that
range!
+0.4.14 2009-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr>