Update TODO list; remove issues from old board ports

configs/c5471evm/README.txt

@@ -31,6 +31,15 @@ Toolchain
   8. Edit setenv.h so that the PATH variable includes the path to the
      newly built binaries.
 
+Issues
+^^^^^^
+
+  Title:       UART RECONFIGURATION
+  Description: UART re-configuration is untested and conditionally compiled out.
+  Status:      Open
+  Priority:    Medium.  ttyS1 is not configured, but not used; ttyS0 is configured
+               by the bootloader
+
 ARM/C5471-specific Configuration Options
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

configs/mx1ads/README.txt

@@ -31,6 +31,22 @@ Toolchain
   8. Edit setenv.h so that the PATH variable includes the path to the
      newly built binaries.
 
+Issues
+^^^^^^
+
+  Title:       PORT IS INCOMPLETE
+  Description: The basic port of the i.MX1 architecture was never finished.  The port
+               is incomplete (as of this writing, is still lacks a timer, interrupt
+               decoding, USB, network) and untested.
+  Status:      Open
+  Priority:    Medium (high if you need i.MX1/L support)
+
+  Title:       SPI METHODS ARE NOT THREAD SAFE
+  Description: SPI methods are not thread safe.  Needs a semaphore to protect from re-entrancy.
+  Status:      Open
+  Priority:    Medium -- Will be very high if you do SPI access from multiple threads.
+
+
 ARM/i.MX1-specific Configuration Options
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

configs/ntosd-dm320/README.txt

@@ -13,6 +13,7 @@ CONTENTS
   - ARM/DM320-specific Configuration Options
   - Configurations
   - Configuration Options
+  - Issues
 
 Dev vs. Production Neuros OSD v1.0 boards
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -395,3 +396,34 @@ Neuros OSD Configuration Options
  CONFIG_ARCH_NTOSD_DEVBOARD - Selects the old NTOSD development board.
    The default is the production OSD board which differs in
    several ways.
+
+Issues
+^^^^^^
+
+  Title:       DEBUG ISSUES
+  Description: config/ntos-dm320: It seems that when a lot of debug statements
+               are added, the system no longer boots.  This is suspected to be
+               a stack problem: Making the stack bigger or removing arrays on
+               the stack seems to fix the problem (might also be the
+               bootloader overwriting memory)
+  Status:      Open
+  Priority:    Medium
+
+  Title:       USB DEVICE DRIVER UNTESTED
+  Description: A USB device controller driver was added but has never been tested.
+  Status:      Open
+  Priority:    Medium
+
+  Title:       FRAMEBUFFER DRIVER UNTESTED
+  Description: A framebuffer "driver" was added, however, it remains untested.
+  Status:      Open
+  Priority:    Medium
+
+  Title:       VIDEO ENCODER DRIVER
+  Description: In order to use the framebuffer "driver" additional video encoder
+               logic is required to setup composite video output or to interface
+               with an LCD.
+  Status:      Open
+  Priority:    Medium (high if you need to use the framebuffer driver)
+
+