X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=testing%2Fsmoketests.html;h=459f8bf69f6eaa810d393d8c3360653da11b3073;hp=a367f08ced97010099e0b91f7ccc6da18c751931;hb=8a162e5e063fbbd6be04568e29633fad8f8b6720;hpb=fcf674ced30d542caccba41a77f494b5a4df23e5
diff --git a/testing/smoketests.html b/testing/smoketests.html
index a367f08ced..459f8bf69f 100644
--- a/testing/smoketests.html
+++ b/testing/smoketests.html
@@ -4,7 +4,8 @@
OpenOCD smoketest results
- These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN.
+ These tests can be performed on any JTAG device as long as they are
+ executed using the unmodified code from git.
The latest version in which the test is known to have passed is in the table below.
Vocabulary
@@ -90,92 +91,92 @@
| bdte-ram1 |
str710 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom2 |
str710 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram3 |
str912 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom4 |
str912 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram5 |
lpc2148 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom6 |
lpc2148 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram7 |
lpc2294 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom8 |
lpc2294 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram9 |
sam7s256 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom10 |
sam7s256 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram11 |
sam7x256 ram debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-rom12 |
sam7x256 rom debugging |
JTAGkey |
- 651 |
+ 657 |
n/a |
| bdte-ram13 |
at91r40008 ram debugging |
JTAGkey |
- 536 |
- 651 |
+ 657 |
+ n/a |
@@ -199,19 +200,19 @@
| jtag2 |
JTAGkey |
- 651 |
+ 657 |
n/a |
| jtag3 |
Turtelizer2 |
- 651 |
+ 657 |
n/a |
| jtag4 |
JTAGkey |
- 651 |
+ 657 |
n/a |
@@ -240,6 +241,7 @@
| r517 |
r536 |
r651 |
+ r657 |
| speed1 |
@@ -251,6 +253,7 @@
93 |
93 |
162 |
+ 165 |
| speed2 |
@@ -262,6 +265,7 @@
52 |
52 |
110 |
+ 111 |
| speed3 |
@@ -273,15 +277,26 @@
n/a |
n/a |
n/a |
+ n/a |
Policy on removing features from OpenOCD
- If a feature in OpenOCD is known to be broken and nobody has submitted a fix and the feature is causing trouble for maintainence, it can be removed from OpenOCD trunk. The threshold for temporarily removing something from OpenOCD trunk is low to ease maintainence and place the burden of maintainence on those that care about a feature.
- Note that code is never deleted from OpenOCD svn, it remains in svn so if somebody sees a feature removed that they would like kept, they have but to port and fix that feature back up to main trunk. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.
+ If a feature in OpenOCD is known to be broken and nobody has submitted
+ a fix and the feature is causing trouble for maintainence, it can be
+ removed from OpenOCD mainline. The threshold for temporarily removing
+ something from OpenOCD mainline is low to ease maintainence and place the burden of maintainence on those that care about a feature.
+ Note that code is never deleted from OpenOCD git, it remains in the
+ repository so if somebody sees a feature removed that they would like
+ kept, they have but to port and fix that feature back up to main
+ mainline. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.
Policy on adding features from OpenOCD
- To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk.
+ To add a feature to OpenOCD, generally it should not break any
+ existing features and it should be functional and the code reasonably
+ readable and useful to others in the OpenOCD community. The code does
+ not have to be completed. Work in progress is fine for OpenOCD
+ mainline.
Also new tests should be defined. Note that the code does not have to pass all the tests. In fact it can be helpful to have tests to describe facets that really should be working, but aren't done yet.
ocd4 - ARM7 debugging
@@ -316,4 +331,4 @@
-