I know it's bad form to ask about when a release might happen, but with
my Debian maintainer hat on I'm aware there's some good stuff that's
landed since 0.10 in January 2017, and it would be good to make that
available in the Debian packages (aarch64 support springs to mind, but
I've also had some
On Wed, May 08, 2019 at 08:32:34PM +0300, Liviu Ionescu wrote:
> I know that OpenOCD uses a rolling distribution model, with all
> commits being considered stable, but is there any new official release
> planned?
>
> 0.10 came in Jan 2017, more than two years ago, and I reached
> 0.10.0-12 for th
On Thu, Feb 13, 2020 at 04:12:30PM -0200, Alain Mouette wrote:
> Is it possible to compile OpenOCD with STlink-v2 to run on a Raspberry
> PI?
>
> Note that I *don't want* do debug the RasPI. I want to use the RasPI
> with OpenOCD _to debug an STM32_ with STlink-v2 I already use OpenOCD
> on Linux
On Wed, Jun 10, 2020 at 04:41:33PM +0300, Liviu Ionescu wrote:
> I'm preparing a new xPack OpenOCD release. Is it ok to use the top of
> the repo? If not, which commit id do you suggest?
FWIW the snapshot I uploaded to Debian/experimental at the end of May
used d8ac0086f957fabf63d596a3b8d396b110bc
On Sat, Dec 12, 2020 at 05:31:21PM +0100, Antonio Borneo wrote:
> OpenOCD v0.11.0 is on the way, maybe in one month from now.
>
> After the v0.11.0 tag, I would like to update the checkpatch
> included in OpenOCD with the current version available in Linux
> code. A preliminary series is already i
On Tue, Dec 22, 2020 at 12:39:20PM +0100, Antonio Borneo wrote:
> In the current cycle of fixes for v0.11.0-rc1 I'm willing to merge the
> following patches, but they got +1 only by me.
> Is there anyone that can review and/or test them?
> Any other patch that should be considered?
>
> http://open
On Sat, Jun 19, 2021 at 01:19:40PM +0100, Tarek BOCHKATI wrote:
> I have seen that you have helped getting openocd 0.11.0-rc2 into both
> bullseye (testing) and sid (unstable). but unfortunately the official
> v0.11.0 release has never made it to buster (stable).
>
> IMO, it would be nice if peop
On Wed, May 18, 2022 at 11:00:58AM +0200, Antonio Borneo wrote:
> Dear OpenOCD developers,
>
> it's probably time to think about a new release of OpenOCD.
> v0.11.0 was tagged in March 2021, more than one year ago.
> There are already 686 commits merged after v0.11.0 covering several
> improvement
On Tue, Sep 06, 2022 at 09:56:34AM +0200, Antonio Borneo wrote:
> The deadline for tagging v0.12.0-rc1, proposed for mid September, is
> approaching. Nothing is fixed in stone, such a deadline is not a hard
> schedule, but I would like to respect it. We already have 832 patches
> merged from the
On Fri, Nov 18, 2022 at 10:46:18AM +0100, Antonio Borneo wrote:
> On Wed, May 18, 2022 at 2:29 PM Antonio Borneo
> wrote:
> > On Wed, May 18, 2022 at 12:23 PM Jonathan McDowell wrote:
> > > Debian is looking at starting to freeze for the next stable release in
> > &
I've been finding reviews.openocd.org very slow over the past few days -
logging in sometimes times out, saving a review takes ages. It always
seems to *eventually* get there and I can't see any sign of networking
issues between me and it. Are there any known issues?
J.
--
] https://www.earth.li
FWIW the Debian package installs the udev rules to
lib/udev/rules.d/60-openocd.rules, as they are part of the package. However
they do not have the 2141 PID in them, just 03eb/204f, so if it was working
before there must have been something extra installed/configured.
---
** [tickets:#258] su
12 matches
Mail list logo
