On Thu, Sep 3, 2020 at 12:57 AM Connor Lansdale
wrote:
>
> Hello! Is there a plan or schedule to release the next stable version? It
> feels like
> it is ready to go and the last official release was some time ago, I'm curious
> what is holding it back. I am happy to help contribute if possible.
Hello! Is there a plan or schedule to release the next stable version? It feels
like it is ready to go and the last official release was some time ago, I'm
curious what is holding it back. I am happy to help contribute if possible.
Thank you,
Connor
Tomas
the changes below are listed in the adapter-driver topic only because
are required by the following changes in the same topic.
But they are generic, not linked with the topic itself, and already approved.
I just retested them on top of current master, to avoid other issues.
Would you mind
On Wed, Jun 5, 2019 at 9:09 AM Tomas Vanek via OpenOCD-devel <
openocd-devel@lists.sourceforge.net> wrote:
> On 05.06.2019 16:10, Matthias Welwarsky wrote:
>
>
>
> I don't see SWD multidrop as a candidate for 0.11 so that can wait, but
> the reset framework is right now so utterly borked that the
On 05.06.2019 16:10, Matthias Welwarsky wrote:
I don't see SWD multidrop as a candidate for 0.11 so that can wait,
but the reset framework is right now so utterly borked that the
breakage spills over into configuration files. Check the R-CarH3 files
for bad examples.
Neither do I. But
Of course, I would like to see the adapter-driver series merged in 0.11.
I did not received any negative feedback, I'm just waiting it get
merged to propose the speed improvement patches on top of it.
There is a minor conflict with the reset series, but easy to manage
I would also like to see the
On Mittwoch, 5. Juni 2019 12:23:11 CEST Tomas Vanek via OpenOCD-devel wrote:
> On 11.05.2019 9:47, matth...@welwarsky.de wrote:
> > I think we're more than ripe for a new release, but there's one patch
> > series that I really want to see merged, which is the reset framework
> > stuff Tomas Vanek
On 11.05.2019 9:47, matth...@welwarsky.de wrote:
I think we're more than ripe for a new release, but there's one patch
series that I really want to see merged, which is the reset framework
stuff Tomas Vanek has done.
Matthias,
I'm afraid it is not wise to wait for any particular patch or
Hi Andreas,
does the silicon bug affect F4 and F7 too?
If not, can you split the patch so to merge only F4 & F7 stuff, and H7 &
L4+ in the new patch you are working on?
I think multiple small patches are better than a big one, and probably
has more chances to be merged.
Il 15/05/19 15:27,
Please note that I'm currently working on some significant changes as
H7, L4+ (and apparently MP1) series suffer from an unpleasant silicon
bug in memory mapped mode ...
On 2019-05-15 14:43, Claudio Lanconelli wrote:
Hello,
can you merge http://openocd.zylin.com/#/c/4321 before next release,
Hello,
can you merge http://openocd.zylin.com/#/c/4321 before next release, please.
I don't think I'm the only one who need support to QSPIFlash on STM32F7
(more than two years old!!!)
Cheers,
Claudio Lanconelli
___
OpenOCD-devel mailing list
> On 14 May 2019, at 15:56, Oleksij Rempel wrote:
>
> Last digit is used as counter n++, not a day.
to me this looks like an inconsistency; even with a clear and detailed
documentation, I doubt you can avoid confusion.
that's the beauty of semver, you don't have to define your own
Am 14.05.19 um 14:41 schrieb Liviu Ionescu:
On 14 May 2019, at 12:40, Oleksij Rempel wrote:
Or we can use just use year and month of release
if you go that route, be sure you include the day too, otherwise for a buggy
release issued at the beginning of the month you have to wait till
> On 14 May 2019, at 12:40, Oleksij Rempel wrote:
>
> Or we can use just use year and month of release
if you go that route, be sure you include the day too, otherwise for a buggy
release issued at the beginning of the month you have to wait till next month
to release a fix.
regards,
Am 13.05.19 um 11:35 schrieb Matthias Welwarsky:
On Samstag, 11. Mai 2019 10:50:03 CEST Liviu Ionescu wrote:
> > On 11 May 2019, at 10:47, matth...@welwarsky.de wrote:
> >
> > I think we're more than ripe for a new release,
>
> super!
>
> > but there's one patch series ... and a
> On 13 May 2019, at 12:35, Matthias Welwarsky wrote:
>
> > what do you think about making periodic releases and possibly adopting
> > semantic versioning (semver)?
>
> Hm. That has a lot of implications.
>
> I cannot see openocd doing major/minor releases, let alone patches. There is
>
On Samstag, 11. Mai 2019 10:50:03 CEST Liviu Ionescu wrote:
> > On 11 May 2019, at 10:47, matth...@welwarsky.de wrote:
> >
> > I think we're more than ripe for a new release,
>
> super!
>
> > but there's one patch series ... and a few kinks ...
>
> sure, I don't think there's a real rush, when
> On 11 May 2019, at 10:47, matth...@welwarsky.de wrote:
>
> I think we're more than ripe for a new release,
super!
> but there's one patch series ... and a few kinks ...
sure, I don't think there's a real rush, when you think the code is ready for a
new release, just let us know.
---
On Mittwoch, 8. Mai 2019 19:32:34 CEST 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
> the GNU
On Thu, May 09, 2019 at 03:50:43PM +0200, kristof.mul...@telenet.be wrote:
> 2. http://openocd.net
>This website is apparently offline for the moment. I remember it was a
> very good-looking
>website. You can visit a snapshot through http://web.archive.org.
>Looking at the (snapshot
Hi @OpenOCD developers,
I really like the initiative from Mr. Liviu Ionescu:
> For a few releases per year I can handle the multi-platform binary
> distribution,
> as I already did. I provide 32/64 Windows, 32/64 Linux, and macOS binaries.
I think it would be great to make these binaries
> On 9 May 2019, at 08:08, Christopher Head wrote:
>
>
> ... Make that three. I think a couple of times a year would be nice, if not
> more often.
Great!
In practical terms, the maintenance overhead is minimal, we only need to add a
new branch to the repository (like 'develop') and
> On 9 May 2019, at 10:09, kristof.mul...@telenet.be wrote:
>
> ... Releases for both Windows and Linux (and why not MacOS) would be great.
for a few releases per year I can handle the multi-platform binary
distribution, as I already did. I provide 32/64 Windows, 32/64 Linux, and macOS
Cc: "openocd-devel"
Verzonden: Woensdag 8 mei 2019 22:33:44
Onderwerp: Re: [OpenOCD-devel] New release?
> On 8 May 2019, at 23:00, Jonathan McDowell wrote:
>
> ... I asked this question back in September and didn't get any responses;
this makes two of us interested in this.
any
On Wed, 8 May 2019 23:33:44 +0300
Liviu Ionescu wrote:
> > On 8 May 2019, at 23:00, Jonathan McDowell wrote:
> >
> > ... I asked this question back in September and didn't get any
> > responses;
>
> this makes two of us interested in this.
>
> anyone else that would like to have a more
> On 8 May 2019, at 23:00, Jonathan McDowell wrote:
>
> ... I asked this question back in September and didn't get any responses;
this makes two of us interested in this.
anyone else that would like to have a more active versioning scheme for the
project?
> I've been pondering whether I
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
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 the
GNU MCU Eclipse OpenOCD distribution, which is a bit unusual.
28 matches
Mail list logo
