Re: [Openocd-development] endstate command

2009-06-07 Thread Øyvind Harboe
On Sun, Jun 7, 2009 at 7:45 PM, David Brownell wrote: > On Sunday 07 June 2009, David Brownell wrote: >> > How about retiring the "endstate" command? >> >> No current in-tree users, FWIW. > > ... except beagleboard init, sorry. Does that usage happen to be broken anyway? -- Øyvind Harboe Embed

Re: [Openocd-development] endstate command

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, David Brownell wrote: > > How about retiring the "endstate" command? > > No current in-tree users, FWIW. ... except beagleboard init, sorry. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists

Re: [Openocd-development] endstate command

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, Øyvind Harboe wrote: > How about retiring the "endstate" command? No current in-tree users, FWIW. Make sure you remove the openocd.texi references to it too ... might want to first merge the openocd.texi "user's guide tweaks" patch I sent last week, so you don't break its

[Openocd-development] endstate command

2009-06-07 Thread Øyvind Harboe
How about retiring the "endstate" command? This command can't work unless polling is turned off as the global endstate gets overwritten by the background polling. If other commands such as "drscan" does not have a clearly defined default end-state then the endstate of such commands is effectively