Great posting! Can I suggest that you create this as a patch against
svn so we can match up the todo.txt list against an actual version of
the OpenOCD svn history?

W.r.t. churn, I think it would be helpful, as you do, to try to get
a lot of those "warning fixes" out of the way so that at least the
overall codebase is a bit more stable and then hopefully the
"churn" is localized to a set of files at any one time.

> * Architectural Upgrades
>  - Allow N:M:P mapping of servers, targets, and interfaces

- About CFI:

I'd like to see if the ecosflash driver could not be used to take
a CFI driver from e.g. eCos and use that in OpenOCD. The
current OpenOCD CFI driver is fine, such as it is, but e.g.
eCos CFI drivers are getting a *LOT* of testing from a much
bigger community.

- New targets?


-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to