[Openocd-development] Change to jtag_add_statemove() - virtex/xilinx support affected

[Ø. H. <oyv...@zy...>]

The attached patch could possibly affect virtex/xsvf support, but
I don't know enough about virtex/xsvf to say.

jtag_add_statemove() is now a no-op if state == current state,
except state == TAP_TLR which always resets the state machine.

Any objections?

jtag_add_statemove() is only used by jtag.c, virtex2.c and xsvf.c.

Why this change you ask?

This is part of clarifying what the jtag_xxx() functions actually mean.

If a statemove to the current state is not a no-op it is something
else and that "something else" has not been defined.

If a very specific path is required, then the correct function to
use is jtag_add_pathmove(), which is unambigous.

-- 
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit