From fa54d4c2ca8ffcece7a9c6e9c784e2150cbed78b Mon Sep 17 00:00:00 2001
From: "Suren A. Chilingaryan" <csa@suren.me>
Date: Sun, 18 Oct 2015 07:36:47 +0200
Subject: Support reading/writting register views by id

---
 docs/ToDo | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

(limited to 'docs/ToDo')

diff --git a/docs/ToDo b/docs/ToDo
index 5575c00..2b7b741 100644
--- a/docs/ToDo
+++ b/docs/ToDo
@@ -1,16 +1,15 @@
 High Priority (we would need it for IPE Camera)
 =============
  1. Join multiple XML files and on error use simplified XSD scheme on all files to find the file causing error
- 2. Universal tree-style api to access the independent views, frontend all registers as well (pci -l /register; pci -r /register/reg1; pci -r /sensor/width;) Unit is path of the view /view[:unit] or just /unit for register vies
- 3. Information on bank and the view values in the pci -i <reg>, show listing of enum values (shall we have a type associated with the view: enum, range, ...?)
- 4. Integrate hash tables for views, units, and registers
+ 2. Information on bank and the view values in the pci -i <reg>, show listing of enum values (shall we have a type associated with the view: enum, range, ...?)
  
 Normal Priority (it would make just few things a bit easier)
 ===============
  1. Implement pcilib_configure_autotrigger
  2. Provide OR and AND operations on registers in cli
  3. Support writting a data from a binary file in cli
- 
+ 4. Support Python-scripts in a views, we need to provide python function to read registers/properties...
+
 Low Priority (only as generalization for other projects)
 ============
  1. Shall we allow overriding of registers?
-- 
cgit v1.2.3