Re: Dummy adapter not built by default

2024-06-02 Thread Tommy Murphy
>>> Therefore, I would turn on support for the dummy adapter in the configure >>> script >>> by default, even if that means compiling support for 'bitbang' by default >>> too. >> >> [...] >> I'm curious about your mention of "bitbang" above - >> what specifically are you referring to there? > > T

Re: Dummy adapter not built by default

2024-06-02 Thread R. Diez
If I had to guess I would presume that the idea is that the Dummy Adapter is only really useful for debugging/diagnostic purposes so it's not enabled by default and if you hit a problem that needs it then you configure and build OpenOCD yourself with it enabled? I have had issues in the past

Re: Underfull warnings from openocd.texi

2024-06-02 Thread R. Diez
I had difficulty visualising this ;-) so had to capture a screenshot which I'm hoping the mailing list can cope with... If it can't then the screenshot is also here: * https://ibb.co/M53SjdM I guess that you mean this? The green box shows a URL fits on a single line an

[PATCH]: 7e35164103 target: Do not use LOG_USER() for error messages

2024-06-02 Thread gerrit
This is an automated email from Gerrit. "zapb " just uploaded a new patch set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/8314 -- gerrit commit 7e3516410337f54a822e38be30bb2ca02350bbe3 Author: Marc Schink Date: Sun Jun 2 14:39:36 2024 +0100 target: Do not use

Re: Underfull warnings from openocd.texi

2024-06-02 Thread Tommy Murphy
> The generated text in the PDF looks indeed weird, that is the reason for the > warnings. Such long URLs are broken into the next line, but the first line is > justified, so the first part of the URL gets moved to the right inside the > line. I had difficulty visualising this ;-) so had to cap

Re: Dummy adapter not built by default

2024-06-02 Thread Tommy Murphy
> But alas, it wasn't supported by my build of OpenOCD. FWIW, as you probably know already, the default for this adapter is "disabled" so it's not enabled unless explicitly enabled at configuration/build time. Whoever built the OpenOCD that you're using presumably didn't enable it? > This is str

[PATCH]: 8e18ee8b20 server/gdb: Use LOG_TARGET_xxx() to show target name

2024-06-02 Thread gerrit
This is an automated email from Gerrit. "zapb " just uploaded a new patch set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/8313 -- gerrit commit 8e18ee8b2090b93e57f7c5f6cdd535a49df59264 Author: Marc Schink Date: Sun Jun 2 12:20:36 2024 +0100 server/gdb: Use LO

Problematic usage of git2cl

2024-06-02 Thread R. Diez
Hi all: The OpenOCD build system is using script git2cl to generate the ChangeLog file for a distribution. This is the invocation in Makefile.am: git --git-dir $(srcdir)/.git log | PERL_UNICODE="IO" $(srcdir)/tools/git2cl/git2cl > $(distdir)/ChangeLog ; \ The upstream source code of git2cl is