This is an automated email from Gerrit.
"Andreas Fritiofson <andreas.fritiof...@gmail.com>" just uploaded a new patch
set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/8669
-- gerrit
commit 6953b78efc8dea35ec4b2be23c7a3381e34cc4a6
Author: Andreas Fritiofson <andreas.fritiof...@gmail.com>
Date: Sun Dec 22 02:43:56 2024 +0100
Remove obsolete non-ARM chapter from developers guide
Change-Id: If3e36a8eab096182a848112b660161ecffdc6d00
Signed-off-by: Andreas Fritiofson <andreas.fritiof...@gmail.com>
diff --git a/doc/manual/main.txt b/doc/manual/main.txt
index c28fbe2288..5bab130185 100644
--- a/doc/manual/main.txt
+++ b/doc/manual/main.txt
@@ -83,7 +83,6 @@ modules are stacked in the current implementation (from
bottom to top):
- @ref jtagdriver
- @subpage targetdocs
- @ref targetarm
- - @ref targetnotarm
- @ref targetmips
- @ref targetregister
- @ref targetimage
diff --git a/doc/manual/target.txt b/doc/manual/target.txt
index 7e9767f8f8..0ce8574e77 100644
--- a/doc/manual/target.txt
+++ b/doc/manual/target.txt
@@ -8,7 +8,6 @@ developed by following or using these APIs.
The Target Support module contains APIs that cover several functional areas:
- @subpage targetarm
- - @subpage targetnotarm
- @subpage targetmips
- @subpage targetregister
- @subpage targetimage
diff --git a/doc/manual/target/notarm.txt b/doc/manual/target/notarm.txt
deleted file mode 100644
index 05a19afc8f..0000000000
--- a/doc/manual/target/notarm.txt
+++ /dev/null
@@ -1,70 +0,0 @@
-/** @page targetnotarm OpenOCD Non-ARM Targets
-
-This page describes outstanding issues w.r.t. non-ARM targets.
-
-@section targetnotarmflash Flash drivers
-
-The flash drivers contain ARM32 code that is used
-to execute code on the target.
-
-This needs to be handled in some CPU independent
-manner.
-
-The ecos flash drivers compile the flash
-driver code to run on the target on the developer
-machine.
-
-Instructions should be written on how to
-compile the target flash drivers. Perhaps
-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
-
-@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
-
-@section targetnotarmsupport Target Support
-
-target.h is relatively CPU agnostic and
-the intention is to move in the direction of less
-instruction set specific.
-
-Non-CPU targets are also supported, but there isn't
-a lot of activity on it in the mailing list currently.
-An example is FPGA programming support via JTAG,
-but also flash chips can be programmed directly
-using JTAG.
-
-@section targetnotarmphy non-JTAG physical layer
-
-JTAG is not the only physical protocol used to talk to
-CPUs.
-
-OpenOCD does not today have targets that use non-JTAG.
-
-The actual physical layer is a relatively modest part
-of the total OpenOCD system.
-
-
-@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.
-
-@section targetnotarmmips MIPS
-
-Currently OpenOCD has a MIPS target defined. This is the
-first non-ARM example of a CPU target
-
- */
--
