Do not submit this patch.
Do not modify / retire any parameter from JTAG API scan functions.
Yes, field.out_mask is not used for ARM Debug, but could be very important for
pure boundary scan test !
Please do not touch the JTAG API at all !
Regards,
Laurent Gauch
http://www.amontec.com
Yes, field.out_mask is not used for ARM Debug, but could
be very important for pure boundary scan test !
This can be done from the calling code and it will be much clearer
what's going on.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Yes it could. But giving this out_mask info to the low layer JTAG API
can really help to accelerate the JTAG interface itself and accelerating
the OpenOCD by the way.
Same for in_check_mask and other _mask parameters.
The best you can do is to write new smaller functions calling the actual
On Wed, May 6, 2009 at 11:10 AM, Laurent Gauch
laurent.ga...@amontec.com wrote:
Yes it could. But giving this out_mask info to the low layer JTAG API can
really help to accelerate the JTAG interface itself and accelerating the
OpenOCD by the way.
This is an extraordinary claim that I do not
On Wed, May 6, 2009 at 11:50 AM, Laurent Gauch
laurent.ga...@amontec.com wrote:
Ųyvind Harboe wrote:
On Wed, May 6, 2009 at 11:10 AM, Laurent Gauch
laurent.ga...@amontec.com wrote:
Yes it could. But giving this out_mask info to the low layer JTAG API can
really help to accelerate the JTAG
It think we should keep them (for now). They do not cause any problems,
a helper to fill in defaults is very simple to write.
But it would be interesting to see some example of how they should be
used to accelerate the JTAG Layer Interface.
Please lets us work on more important stuff, 7 step
On Wed, May 6, 2009 at 12:06 PM, Magnus Lundin lun...@mlu.mine.nu wrote:
It think we should keep them (for now). They do not cause any problems,
a helper to fill in defaults is very simple to write.
The helper function is there already. We can introduce
any number of new fields to that
Øyvind Harboe wrote:
These fields are not gone as such. We can have any number of
them that we want by modifying the helper functions.
Lets start with profiling and analysis of OpenOCD and we'll add
those features to the driver API that we need without complicating
the calling code.
I
Oyvind [removed some non-used api features of the JTAG field structures]
Laurent [please put them back, they are important]
Laurent,
You are the only one who wants this to remain.
Your request to keep these items sound like a idea that somebody
_thought_ was important, but it turned out
