todo.md

-## Things to fix and add in ZIO
+## Things we may want to fix or add in ZIO
 
 ### Code Changes
 
   - Add support to write a binary control block in /sys to set a new
-    configuration 
+    configuration (an implementation is pending for approval)
 
 <!-- end list -->
 
@@ -14,10 +14,6 @@
 A discussion of our suggestion for these is on the mailing list archive:
 http://lists.ohwr.org/sympa/arc/zio/2011-11/msg00026.html
 
-  - Interleaved channels
-
-<!-- end list -->
-
   - Double buffering
 
 <!-- end list -->
@@ -32,10 +28,6 @@ http://lists.ohwr.org/sympa/arc/zio/2011-11/msg00026.html
 
   - Tag complex data structures
 
-<!-- end list -->
-
-  - Implement channel flags and alarms
-
 ### New Drivers
 
   - Complete and publish the line discipline for uart-driven input and
@@ -43,38 +35,15 @@ http://lists.ohwr.org/sympa/arc/zio/2011-11/msg00026.html
 
 <!-- end list -->
 
-  - Write zio-tzero, a zio-zero driver with internal timing for samples
-    (or add it to zio-zero)
+  - (low priority) Write zio-tzero, a zio-zero driver with internal
+    timing for samples (or add it to zio-zero)
 
 <!-- end list -->
 
-  - Add internal timing to zio-gpio
-
-<!-- end list -->
-
-  - Write a buffers/zio-buf-circ, a buffer that discards control
-    structures and regenerates them as needed, to reduce overhead when
-    little blocks are used.
+  - (low priority) Add internal timing to zio-gpio
 
 <!-- end list -->
 
   - Write more drivers for real hardware (accelerometers, DACs and so
     on)
 
-### Audit, Consistency, Documentation
-
-  - Update documentation to really reflect code status
-
-<!-- end list -->
-
-  - Audit all spinlocks and related stuff, writing a policy for drivers
-    triggers and buffer
-
-<!-- end list -->
-
-  - Audit all allocations, again writing a policy document
-
-<!-- end list -->
-
-  - Offer defaults in zio-core wherever possible, likes push\_block
-