On Tuesday 25 August 2009, Michael Schwingen wrote:
> > That one example shouldn't go *between* the @deffn blocks ...
> > it's part of the preceding @deffn, giving the bit semantics,
> > not a free-standing chunk of text.
> >
>
> I must admit I do know nothing about texinfo.
>
> How about this
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
David Brownell wrote:
> That one example shouldn't go *between* the @deffn blocks ...
> it's part of the preceding @deffn, giving the bit semantics,
> not a free-standing chunk of text.
>
I must admit I do know nothing about texinfo.
How about this version?
cu
Michael
Index: src/target/xscal
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hi,
it seems the XScale vector table handling code in OpenOCD is only partially
implemented: the code to use user-provided vectors is there, but there is no
way to set these variables, and also no code that syncs the cached vectors
with the RAM contents.
The attached patch adds a "xscale vector_t
