Re: [Openocd-development] Converge towards 0.2?

[Rick Altherr]

On Apr 11, 2009, at 11:48 PM, Øyvind Harboe wrote:

- Changing JTAG state transitions to use shortest path rather than 7 clocks

- Fixing all the drivers that assumed 7 clocks per transition

Why would you want to change this? We've got pathmove for those cases
where the path matters...?

Performance is certainly one reason. Getting correct behavior without using pathmove is another. The target that started all this doesn't _work_ unless you use the shortest path between states. pathmove is fine for special circumstances, but when a variant of a target needs the shortest path, either the target gets changed to use pathmove for everything or you just make normal state movement work better.

- Cortex-A8 support


items that I missed?

The first 2 seem to have good progress being made while the 3rd has had some initial discovery but no real development. Would it be reasonable to start a 0.2 branch after the first 2 items are resolved? Are there other major

into the future + a major new feature...

I think Cortex-A8 would be a good milestone to release against. It is a bit

I was mainly concerned with various distributions and packagers using SVN snapshots again rather than the released version. I'm all for doing a release after Cortex-A8 support is in, but is it reasonable to put out an interim release?

--
Rick Altherr
kc8...@kc8apf.net


with him."
 -- Unsigned




_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

"He said he hadn't had a byte in three days. I had a short, so I split it

--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html

--
Rick Altherr
kc8...@kc8apf.net


 -- Unsigned

"He said he hadn't had a byte in three days. I had a short, so I split it with him."

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development