Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-12-02 Thread Anthony Ferranti via OpenOCD-devel
Antonio, Here is a summary of the specific patches I was referring to and their current status... These patches are add useful features and bug fixes, such as the ability to step a single core in an SMP system, the ability to read ARMv8 system registers regardless of the exception level,

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-12-02 Thread Marc Schink
Tim, do you have any plans to push your changes directly to Gerrit? If not, what's the reason? Marc On Mon, 2020-11-30 at 12:24 -0800, Tim Newsome wrote: > Personally I'm waiting on 0.11 to be finalized (or on a separate > branch) before pushing more changes from the RISC-V fork upstream, so >

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-12-02 Thread Anthony Ferranti via OpenOCD-devel
Ampere Computing is working on the changes requested during code review of the patches submitted by dgoeh...@os.amperecomputing.com. This includes the patches for ADIv6 support and a number of Arm v8 enhancements. Given Arm's recent fanfare regarding the SystemReady program (formerly Arm

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-11-30 Thread Tim Newsome
Personally I'm waiting on 0.11 to be finalized (or on a separate branch) before pushing more changes from the RISC-V fork upstream, so the sooner that happens the better. Tim On Fri, Nov 27, 2020 at 9:51 AM Antonio Borneo wrote: > Hello, > > the initial idea was to tag v0.11.0-rc1 before mid

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-11-27 Thread Antonio Borneo
Hello, the initial idea was to tag v0.11.0-rc1 before mid November, but we have seen big efforts to include other commits. I think it was good to wait a little and get everything more calm. There are still the two commits highlighted by Tomas http://openocd.zylin.com/5729

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-26 Thread Tomas Vanek via OpenOCD-devel
Hi colleagues maintainers/+2 reviewers! http://openocd.zylin.com/5729 "arm_adi_v5: prevent possibly endless recursion in dap_dp_init()" is the fix of IMO serious problem. The patch has already got score +1. Considering it touches a very important part of code, I'd feel more comfortable if it

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-23 Thread Antonio Borneo
Hi all, what about change #5244 "jep106: Add new IDs from JEDEC"? http://openocd.zylin.com/5244/ Should we merge it, or do we need to look for a lawyer? Or ask jedec? Actually there is a new version JEP106BB Jun 2020, but that's not the key point. The current code is based on JEP106AT Sep 2016.

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-20 Thread Antonio Borneo
On Mon, Oct 19, 2020 at 11:25 PM Christopher Head wrote: ... > Finally, I’d also like to see the big reset refactor happen; ... I also would really love to see the reset refactor merged, and also my series http://openocd.zylin.com/#/q/topic:commands-rework but they are both quite invasive,

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-19 Thread Christopher Head
Glad to hear this is happening! Here’s my wishlist for changes I’d like to see. Of course this is only one person’s opinion. 5235, 5236, and 5237 are a few profiling-related changes by me, the first allowing starting profiling without halting the processor first (pretty much essential for a

Re: [OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-19 Thread Tarek BOUCHKATI
Hi Paul, Finally, the long waited release cycle is starting ... I will be glad to help on this, by reviewing, testing and fixing if possible. > So if you have some particular changes you want to see included please speak > up now, and help with testing and reviewing. If you have any issues with

[OpenOCD-devel] The next OpenOCD release is near, get ready

2020-10-19 Thread Paul Fertser
Hello, Thanks to the massive efforts of the developers and maintainers involved (and I would like to specifically mention Antonio Borneo here) we seem to have gained enough momentum to be able to make another OpenOCD release pretty soon. If everything goes according to the plan, the first