-Some outstanding issues w.r.t. non-ARM32 targets
-================================================
-This file describes outstanding issues w.r.t.
-non-ARM32 targets.
+/** @page targetnotarm OpenOCD Non-ARM Targets
-Ideas & patches welcome!
+This page describes outstanding issues w.r.t. non-ARM targets.
+@section targetnotarmflash Flash drivers
-
-
-Flash drivers
--------------
The flash drivers contain ARM32 code that is used
to execute code on the target.
using automake?
-
eCos has CFI driver that could probably be compiled
for all targets. The trick is to figure out a
way to make the compiled flash drivers work
on all target memory maps + sort out all the
little details
-32 vs. 64 bit
--------------
+@section targetnotarm32v64 32 vs. 64 bit
+
Currently OpenOCD only supports 32 bit targets.
Adding 64 bit support would be nice but there
hasn't been any call for it in the openocd development
mailing list
-target support
---------------
+@section targetnotarmsupport Target Support
+
target.h is relatively CPU agnostic and
the intention is to move in the direction of less
instruction set specific.
but also flash chips can be programmed directly
using JTAG.
-non-JTAG physical layer
------------------------
+@section targetnotarmphy non-JTAG physical layer
+
JTAG is not the only physical protocol used to talk to
CPUs.
of the total OpenOCD system.
-PowerPC
--------
+@section targetnotarmppc PowerPC
+
there exists open source implementations of powerpc
target manipulation, but there hasn't been a lot
of activity in the mailing list.
-MIPS
-----
+@section targetnotarmmips MIPS
+
Currently OpenOCD has a MIPS target defined. This is the
-first non-ARM example of a CPU target
\ No newline at end of file
+first non-ARM example of a CPU target
+
+ */